AI agents invoke strato.rpc to trigger actions in Griphook. 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.
JSON-RPC proxying on a blockchain/DeFi platform allows arbitrary calls including contract execution, state-changing transactions, and potentially financial operations. Since the tool accepts arbitrary RPC requests, the most severe applicable category is Execute (and could encompass Financial or Destructive depending on what RPC methods are called).
From the tool's definition "Proxy a JSON-RPC request through the backend RPC router" — arbitrary JSON-RPC calls can execute smart contracts, send transactions, or trigger any blockchain operation
Attacks that exploit this kind of access
Proxy a JSON-RPC request through the backend RPC router. It is categorised as a Execute tool in the Griphook MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Griphook MCP server in PolicyLayer and add a rule for strato.rpc: 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 Griphook. Nothing to install.
strato.rpc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the strato.rpc 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 strato.rpc. 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.
strato.rpc is provided by the Griphook MCP server (strato-net/strato-griphook). 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 →