AI agents call get_account to retrieve information from Codecks without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user account information without creating, modifying, deleting, or executing any operations. It is a straightforward read/query operation with minimal blast radius—the returned data is non-sensitive organizational metadata that an agent could safely access. No financial transactions, destructive actions, or code execution are involved.
From the tool's definition Tool name is 'get_account' and description explicitly states it 'Get[s] current account info (name, id, email, role)' — a read-only retrieval of account metadata with no modification or side effects.
Attacks that exploit this kind of access
Get current account info (name, id, email, role). It is categorised as a Read tool in the Codecks MCP Server, which means it retrieves data without modifying state.
Register the Codecks MCP server in PolicyLayer and add a rule for get_account: 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 Codecks. Nothing to install.
get_account 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_account 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_account. 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_account is provided by the Codecks MCP server (rangogamedev/codecks-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 →