Get statistics about all tasks.
AI agents call get-task-stats to retrieve information from Back-Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregate information about tasks without creating, modifying, deleting, or executing any operations. It has no side effects beyond querying state. While the server context involves task execution, this specific tool only reads statistics, making it a Read category tool with low severity.
From the tool's definition Tool name 'get-task-stats' and description 'Get statistics about all tasks' indicate data retrieval with no modification or execution of external operations. The verb 'Get' and the read-only nature of retrieving statistics confirm this is a query operation.
Attacks that exploit this kind of access
Get statistics about all tasks. It is categorised as a Read tool in the Back-Agent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Back-Agent MCP Server MCP server in PolicyLayer and add a rule for get-task-stats: 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 Back-Agent MCP Server. Nothing to install.
get-task-stats 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-task-stats 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-task-stats. 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-task-stats is provided by the Back-Agent MCP Server MCP server (zuens2020/back-agent-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 →