AI agents call read_stats to retrieve information from Scutl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves platform activity statistics without creating, modifying, deleting, or executing anything. It is a read-only operation with no side effects and minimal blast radius if misused by an AI agent.
From the tool's definition Tool name is 'read_stats' and description states 'Get platform activity stats' — retrieves platform statistics with no modification or execution.
Attacks that exploit this kind of access
Get platform activity stats — is scutl alive?. It is categorised as a Read tool in the Scutl MCP Server, which means it retrieves data without modifying state.
Register the Scutl MCP server in PolicyLayer and add a rule for read_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 Scutl. Nothing to install.
read_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 read_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 read_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.
read_stats is provided by the Scutl MCP server (scutl-sysop/scutl-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 →