rpc_release_all_handles · Rpcclient MCP: Risk & Policy

WHAT IT DOES

What rpc_release_all_handles does on Rpcclient

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

WHY IT NEEDS A POLICY

Why rpc_release_all_handles needs a policy

An AI agent can call rpc_release_all_handles faster than any human can review — one bad instruction and it creates or modifies resources in Rpcclient by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rpc_release_all_handles Rate-limited

rpc_release_all_handles 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": {
    "rpc_release_all_handles": {
      "limits": [
        {
          "counter": "rpc_release_all_handles_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Rpcclient, so you can run agents against it safely.

FAQ

Questions about rpc_release_all_handles

What does the rpc_release_all_handles tool do? +

Release all stored object handles in a session. It is categorised as a Write tool in the Rpcclient MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on rpc_release_all_handles? +

Register the Rpcclient MCP server in PolicyLayer and add a rule for rpc_release_all_handles: 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 Rpcclient. Nothing to install.

What risk level is rpc_release_all_handles? +

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

Can I rate-limit rpc_release_all_handles? +

Yes. Add a rate_limit block to the rpc_release_all_handles 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 rpc_release_all_handles completely? +

Set action: deny in the PolicyLayer policy for rpc_release_all_handles. 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 rpc_release_all_handles? +

rpc_release_all_handles is provided by the Rpcclient MCP server (appknox/rpcclient-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.