Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Revoke Port Access Key

revoke_access_key
DestructiveIdempotent

Revoke a pod port's access key to invalidate its value immediately; use confirm=false to preview and confirm=true to apply, since revocation cannot be undone.

Instructions

Revoke one access key of a pod's port so that its value stops working. It can't be undone; a new key has a new value. With confirm=false (default) it only returns which key would be revoked and changes nothing; call again with confirm=true and the summary's pod_name after the user agreed. The value stops working within seconds, and so does an older value that still worked after a roll. Programs that send it then get 401. A connection that is already open, such as a WebSocket, stays open until it closes. Only a workspace admin or billing member can revoke keys. To replace a key's value without an outage, use roll_access_key instead. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pod": "<pod>",
      "port": "<port>",
      "key_id": "<key_id>"
    },
    "name": "revoke_access_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
podYesThe pod_name from the pods tool. Its display name also works, except on a confirmed call (confirm=true) that opens a port, changes a key or signs out browsers: use the `pod_name` the preview returned.
portYesThe port number, from the pod's `endpoints` in the pods tool; it must be exposed over HTTPS (`access` locked or unlocked).
key_idYesThe key's `id` from the access_keys tool.
confirmNo
workspaceNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructive/openWorld, but the description adds what they cannot: irreversibility with a new key value, the seconds-level propagation delay, the 401 consequence for programs, and the subtle edge case that an already-open WebSocket survives until it closes. It also documents the operation_id lifecycle and post-timeout recovery, which is real behavioral context beyond structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the effect and the safety instructions, then consequences, then permissions, then the operation_id contract — a sensible order with no filler. It is dense and long for one tool, and the trailing operation_id paragraph partly restates the confirm guidance, which keeps it short of a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive 6-parameter write with an output schema, the description covers safety, permissions, timing, side effects, parameter sourcing, and retry behavior. Since the output schema exists, it correctly omits return-value documentation and still names the `pod_name` field the preview returns.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%, and the description compensates: it defines confirm's preview-vs-apply semantics, tells the agent to pass the summary's `pod_name` on the confirmed call rather than a display name, and explains operation_id reuse/regeneration rules. These are non-obvious constraints the schema alone does not convey.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource ("Revoke one access key of a pod's port") plus the effect ("its value stops working"), and explicitly contrasts with roll_access_key, so an agent can distinguish it from the sibling without reading either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the two-step confirm flow with the default preview, names the case for the alternative tool ("To replace a key's value without an outage, use roll_access_key instead"), and gives the authorization precondition (workspace admin or billing member). When-to-use and when-not-to-use are both explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.