Health check: is the browser ready, what egress IP, any recent challenge?
AI agents call session_status to retrieve information from Meta Ad Library MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about the session without performing any actions that modify data, execute code, or trigger external operations. It is a diagnostic/monitoring function that simply reports state information, making it a Read operation with low severity since it poses minimal risk if misused by an AI agent.
From the tool's definition Tool description states it performs a 'Health check' to verify browser readiness, egress IP, and recent challenges—purely informational queries with no modification or execution capabilities.
Attacks that exploit this kind of access
Health check: is the browser ready, what egress IP, any recent challenge?. It is categorised as a Read tool in the Meta Ad Library MCP MCP Server, which means it retrieves data without modifying state.
Register the Meta Ad Library MCP server in PolicyLayer and add a rule for session_status: 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 Ad Library MCP. Nothing to install.
session_status 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 session_status 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 session_status. 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.
session_status is provided by the Meta Ad Library MCP server (konstantin-tradient/meta-ad-library-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 →