Lists users who have access to an ad account with their roles. Args: - ad_account_id (string): Ad account ID (e.g., act_123456789)
AI agents call meta_get_ad_account_users to retrieve information from Meta MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of ad account user access and roles. It retrieves data without side effects, making it a Read category tool. Severity is low because unauthorized access to this information, while potentially sensitive, does not enable direct harm—it only reveals who has permissions on an ad account, not credentials or financial data.
From the tool's definition The tool "lists users" and "their roles" with no mention of modification, deletion, or execution of commands. It purely retrieves and queries access control information.
Documented attack patterns abuse exactly the kind of access meta_get_ad_account_users gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Meta MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for meta_get_ad_account_users:
{
"version": "1",
"default": "deny",
"tools": {
"meta_get_ad_account_users": {}
}
} meta_get_ad_account_users 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.
Lists users who have access to an ad account with their roles. Args: - ad_account_id (string): Ad account ID (e.g., act_123456789). It is categorised as a Read tool in the Meta MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Meta MCP Server MCP server in PolicyLayer and add a rule for meta_get_ad_account_users: 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 MCP Server. Nothing to install.
meta_get_ad_account_users 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 meta_get_ad_account_users 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 meta_get_ad_account_users. 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.
meta_get_ad_account_users is provided by the Meta MCP Server MCP server (oliverames/meta-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Meta MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
200 Meta MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.