AI agents call get_analytics to retrieve information from Seven without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves account statistics and analytics data without creating, modifying, or deleting any resources. It is a read-only query operation that presents no blast radius for accidental misuse by an AI agent.
From the tool's definition Tool name is 'get_analytics' and description states 'Get account statistics and analytics' — purely a data retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
Get account statistics and analytics. It is categorised as a Read tool in the Seven MCP Server, which means it retrieves data without modifying state.
Register the Seven MCP server in PolicyLayer and add a rule for get_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 Seven. Nothing to install.
get_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 get_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 get_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.
get_analytics is provided by the Seven MCP server (seven-io/seven-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 →