AI agents call get_agent_performance_today to retrieve information from Zendesk without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries performance metrics and ticket information without creating, modifying, deleting, or executing any operations. It has minimal blast radius as it only exposes read-only performance analytics data that would typically be accessible to managers/admins reviewing team statistics.
From the tool's definition Tool returns agent performance data including names, counts, and sample tickets. The verb 'Get' and description indicating it 'Returns' data confirms this is a retrieval operation with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get agent performance ranking by tickets solved on a date. Returns names, counts, and sample tickets. It is categorised as a Read tool in the Zendesk MCP Server, which means it retrieves data without modifying state.
Register the Zendesk MCP server in PolicyLayer and add a rule for get_agent_performance_today: 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 Zendesk. Nothing to install.
get_agent_performance_today 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_agent_performance_today 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_agent_performance_today. 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_agent_performance_today is provided by the Zendesk MCP server (kalchevs/zendesk-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 →