get_topic_distribution_tool
AI agents call get_topic_distribution_tool to retrieve information from Email Insights without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries email topic distributions from the analytics database. No modification, deletion, code execution, or financial action occurs. It retrieves structured data for analysis, consistent with the server's read-focused design. The empty description prevents higher confidence, but the context and naming strongly suggest a non-destructive data retrieval operation.
From the tool's definition Tool name 'get_topic_distribution_tool' indicates a retrieval operation. Server description emphasizes 'analytics' and 'query' capabilities with a 'SQLite-backed interface' for extracting and querying email data.
Attacks that exploit this kind of access
get_topic_distribution_tool. It is categorised as a Read tool in the Email Insights MCP Server, which means it retrieves data without modifying state.
Register the Email Insights MCP server in PolicyLayer and add a rule for get_topic_distribution_tool: 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 Email Insights. Nothing to install.
get_topic_distribution_tool 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_topic_distribution_tool 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_topic_distribution_tool. 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_topic_distribution_tool is provided by the Email Insights MCP server (shubby98/email-insights). 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 →