AI agents call get_analytics to retrieve information from Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves analytics metrics without creating, modifying, deleting, or executing any operations. It is a pure data query operation with no side effects, fitting the Read category. The low severity reflects minimal risk from misuse—retrieving analytics data poses no risk of data loss, financial impact, or system compromise.
From the tool's definition Tool name 'get_analytics' and description 'Get analytics data for a metric' indicate data retrieval with no modification capability. The phrase 'Get analytics data' explicitly describes a read operation.
Attacks that exploit this kind of access
Get analytics data for a metric (registered via forFeature). It is categorised as a Read tool in the Server MCP Server, which means it retrieves data without modifying state.
Register the Server 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 Server. 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 Server MCP server (@nest-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 →