Fetch details for a single Meta ad account including spend cap, balance, and amount spent today.
AI agents call get_ad_account to retrieve information from Claude Meta without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account metadata (spend cap, balance, amount spent today) without creating, modifying, deleting, or executing any operations. It is a passive read-only query. Severity is low because account details alone do not enable direct resource abuse or financial transactions, though the information could inform downstream misuse via sibling write/destructive tools.
From the tool's definition Tool name is 'get_ad_account' and description states 'Fetch details' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Fetch details for a single Meta ad account including spend cap, balance, and amount spent today. It is categorised as a Read tool in the Claude Meta MCP Server, which means it retrieves data without modifying state.
Register the Claude Meta MCP server in PolicyLayer and add a rule for get_ad_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 Claude Meta. Nothing to install.
get_ad_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_ad_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_ad_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_ad_account is provided by the Claude Meta MCP server (maxx3250/claude-meta-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 →