rpc_connect · Rpcclient MCP: Risk & Policy

WHAT IT DOES

What rpc_connect does on Rpcclient

AI agents invoke rpc_connect to trigger actions in Rpcclient. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why rpc_connect needs a policy

Establishing a remote session to an iOS RPC server initiates an external connection that enables subsequent automation actions (launching apps, clicking, typing, gestures). While the connection itself doesn't destructively modify data, it triggers an external operation and opens a privileged channel for further actions, placing it firmly in Execute.

From the tool's definition Create an rpcclient session to a remote rpcserver target

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rpc_connect Rate-limited

rpc_connect stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_connect": {
      "limits": [
        {
          "counter": "rpc_connect_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_connect

What does the rpc_connect tool do? +

Create an rpcclient session to a remote rpcserver target. It is categorised as a Execute tool in the Rpcclient MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rpc_connect? +

Register the Rpcclient MCP server in PolicyLayer and add a rule for rpc_connect: 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_connect? +

rpc_connect is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rpc_connect? +

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

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

rpc_connect 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.