Execute any method on the Keeta Client (read-only network operations). Use keeta_list_sdk_methods with target
AI agents call keeta_client_execute to retrieve information from Keeta Network MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The description states this tool performs read-only network operations on the Keeta blockchain. However, the name 'execute' and the dynamic/self-describing architecture of the server (which allows agents to discover and execute SDK methods at runtime) introduces some uncertainty about whether truly all callable methods are non-mutating.
From the tool's definition 'Execute any method on the Keeta Client (read-only network operations)' — explicitly described as read-only
Attacks that exploit this kind of access
Execute any method on the Keeta Client (read-only network operations). Use keeta_list_sdk_methods with target. It is categorised as a Read tool in the Keeta Network MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Keeta Network MCP Server MCP server in PolicyLayer and add a rule for keeta_client_execute: 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 Keeta Network MCP Server. Nothing to install.
keeta_client_execute 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 keeta_client_execute 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 keeta_client_execute. 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.
keeta_client_execute is provided by the Keeta Network MCP Server MCP server (schenkty/kta-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 →