AI agents call get_account_info to retrieve information from Meta Ads MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the naming convention strongly indicates this is a read operation that queries Meta account information without side effects. However, confidence is not higher (0.85 rather than 0.95+) because the description lacks detail, and 'account info' could potentially include sensitive data like billing details or contact information, warranting at least a 'medium' severity rating.
From the tool's definition Tool name 'get_account_info' uses the 'get_' prefix, a standard pattern for read operations that retrieve data without modification.
Documented attack patterns abuse exactly the kind of access get_account_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta Ads MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_account_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_account_info": {}
}
}get_account_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_account_info. It is categorised as a Read tool in the Meta Ads MCP MCP Server, which means it retrieves data without modifying state.
Register the Meta Ads MCP server in PolicyLayer and add a rule for get_account_info: 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 Meta Ads MCP. Nothing to install.
get_account_info 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_info 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_info. 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_info is provided by the Meta Ads MCP server (pipeboard-co/meta-ads-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 42 Meta Ads MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
42 Meta Ads MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.