Retrieves a specific rule from a policy.
AI agents call get_policy_rule to retrieve information from Privy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval without modification, deletion, or execution of blockchain operations. The verb 'retrieves' clearly indicates a Read category operation. Even within the context of a blockchain wallet management server with tools like eth_sendTransaction and create_wallet, this specific tool is limited to querying policy rule data. Low severity due to minimal blast radius if misused by an AI agent.
From the tool's definition Tool description states 'Retrieves a specific rule from a policy' - retrieves indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
Retrieves a specific rule from a policy. It is categorised as a Read tool in the Privy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Privy MCP Server MCP server in PolicyLayer and add a rule for get_policy_rule: 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 Privy MCP Server. Nothing to install.
get_policy_rule 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 get_policy_rule 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 get_policy_rule. 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.
get_policy_rule is provided by the Privy MCP Server MCP server (privy-io/privy-mcp-server). 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 →