AI agents call rpc_list_sessions to retrieve information from Rpcclient without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely enumerates or retrieves information about active sessions. It has no side effects, does not execute operations on iOS devices, and does not modify or destroy data. While the server context involves iOS automation with potential for misuse, this specific tool only reads/lists state.
From the tool's definition Tool name 'rpc_list_sessions' and description 'List active rpcclient sessions' indicate a query operation that retrieves metadata about existing sessions without modifying, executing commands, or deleting data.
Attacks that exploit this kind of access
List active rpcclient sessions. It is categorised as a Read tool in the Rpcclient MCP Server, which means it retrieves data without modifying state.
Register the Rpcclient MCP server in PolicyLayer and add a rule for rpc_list_sessions: 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.
rpc_list_sessions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the rpc_list_sessions 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.
Set action: deny in the PolicyLayer policy for rpc_list_sessions. 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.
rpc_list_sessions 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →