Inspects the current Meta access token to show its type, expiry, permissions, and associated app/user. Useful for diagnosing
AI agents call meta_debug_token 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 retrieves and displays information about an existing access token (its type, expiry, permissions, app/user association). It performs no modifications, deletions, or external operations. While token inspection could theoretically expose sensitive information, the action itself is a passive read operation.
From the tool's definition Tool name 'meta_debug_token' and description: 'Inspects the current Meta access token to show its type, expiry, permissions, and associated app/user.' The verb 'inspects' and 'show' indicate read-only retrieval of token metadata with no side effects.
Documented attack patterns abuse exactly the kind of access meta_debug_token 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_debug_token:
{
"version": "1",
"default": "deny",
"tools": {
"meta_debug_token": {}
}
} meta_debug_token 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.
Inspects the current Meta access token to show its type, expiry, permissions, and associated app/user. Useful for diagnosing. 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_debug_token: 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_debug_token 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_debug_token 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_debug_token. 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_debug_token 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.