Execute any method on the Keeta UserClient (authenticated operations requiring an account). Use keeta_list_sdk_methods with target
AI agents use keeta_user_client_execute to commit financial operations through Keeta Network MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool executes arbitrary authenticated operations on a Layer 1 blockchain client. Given the server's explicit purpose of payments and asset transfers, authenticated user client methods almost certainly include sending transactions, transferring assets, and other financial operations.
From the tool's definition 'Execute any method on the Keeta UserClient (authenticated operations requiring an account)' on a server described as providing 'payments, asset transfers, and compliance-ready financial infrastructure'
Attacks that exploit this kind of access
Execute any method on the Keeta UserClient (authenticated operations requiring an account). Use keeta_list_sdk_methods with target. It is categorised as a Financial tool in the Keeta Network MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Keeta Network MCP Server MCP server in PolicyLayer and add a rule for keeta_user_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_user_client_execute is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the keeta_user_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_user_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_user_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 →