AI agents call stape_container_analytics to retrieve information from Stape without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool primarily retrieves and queries analytics data, which is a read operation. While enabling/disabling analytics involves toggling settings (which could be categorized as Write), the core function is data retrieval and monitoring.
From the tool's definition Tool supports 'getting analytics info, browser analytics, client analytics' and 'enabling/disabling analytics'. The primary operations are retrieval ('getting') and toggling settings, with no modification of user data or destructive operations mentioned.
Attacks that exploit this kind of access
Comprehensive tool for managing container analytics. Supports getting analytics info, browser analytics, client analytics, and enabling/disabling analytics. Use the. It is categorised as a Read tool in the Stape MCP Server, which means it retrieves data without modifying state.
Register the Stape MCP server in PolicyLayer and add a rule for stape_container_analytics: 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 Stape. Nothing to install.
stape_container_analytics 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 stape_container_analytics 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 stape_container_analytics. 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.
stape_container_analytics is provided by the Stape MCP server (stape-mcp-server). 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 →