revoke_readonly_invite

SERVERVaultPilot MCP SOURCEvaultpilot-mcp

Medium RISK CLASS

Category Write

Parameters 11 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-szhygulin-vaultpilot-mcp/revoke-readonly-invite.md

WHAT IT DOES

What revoke_readonly_invite does on VaultPilot MCP

AI agents use revoke_readonly_invite to create or update resources in VaultPilot MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultPilot MCP environment.

Parameter	Type	Required	Description
`name`	string	Yes

Parameters from the server's own tool schema.

RISK

Why revoke_readonly_invite is rated Medium

This tool only updates an internal bookkeeping record to mark an invite as revoked. It does not actually revoke access (the token remains valid), does not delete data irreversibly, does not execute code, and has no financial impact. It is a reversible write operation (a status update) with limited real-world effect.

From the tool's definition 'Marks the issuer-side record as revoked at the current time' and 'issuer-side BOOKKEEPING — it does NOT recall the token already in the recipient's hands'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs revoke_readonly_invite safely

PolicyLayer is an MCP gateway: it sits between your AI agents and VaultPilot MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For revoke_readonly_invite, this is the rule to start with:

revoke_readonly_invite Rate-limited

revoke_readonly_invite stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "revoke_readonly_invite": {
      "limits": [
        {
          "counter": "revoke_readonly_invite_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect VaultPilot MCP, apply this rule, and every revoke_readonly_invite call is checked against it from then on.

FAQ

Questions about revoke_readonly_invite

What does the revoke_readonly_invite tool do? +

Revoke a previously-generated read-only share invite by name. Marks the issuer-side record as revoked at the current time. Important caveat (Model A): this is issuer-side BOOKKEEPING — it does NOT recall the token already in the recipient's hands. Anyone holding the raw token can still query the listed addresses (chain reads are public regardless of whether the issuer wants the share to continue). Genuine recall requires Model B (hosted enforcement endpoint), deferred. Returns { revoked: { id, name, revokedAt } } on success; refuses if the name is unknown or already revoked. It is categorised as a Write tool in the VaultPilot MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does revoke_readonly_invite accept? +

revoke_readonly_invite accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on revoke_readonly_invite? +

Register the VaultPilot MCP server in PolicyLayer and add a rule for revoke_readonly_invite: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches VaultPilot MCP. Nothing to install.

What risk level is revoke_readonly_invite? +

revoke_readonly_invite is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit revoke_readonly_invite? +

Yes. Add a rate_limit block to the revoke_readonly_invite rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block revoke_readonly_invite completely? +

Set action: deny in the PolicyLayer policy for revoke_readonly_invite. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides revoke_readonly_invite? +

revoke_readonly_invite is provided by the VaultPilot MCP server (vaultpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on VaultPilot, and thousands of servers like it.

This server

All 189 VaultPilot tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →