Database counts for jobs (by status, type, salary) and conferences.
AI agents call get_stats to retrieve information from Local Tech Digest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries pre-computed statistical data (counts aggregated by various dimensions). It performs no modifications, deletions, executions, or financial operations. It is a straightforward Read operation with minimal risk—an agent querying stats cannot cause harm to the system or data integrity.
From the tool's definition Tool name 'get_stats' and description 'Database counts for jobs (by status, type, salary) and conferences' indicate retrieval of aggregate statistics without modification. No side effects or actions are implied by querying counts.
Attacks that exploit this kind of access
Database counts for jobs (by status, type, salary) and conferences. It is categorised as a Read tool in the Local Tech Digest MCP Server, which means it retrieves data without modifying state.
Register the Local Tech Digest MCP server in PolicyLayer and add a rule for get_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 Local Tech Digest. Nothing to install.
get_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_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_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_stats is provided by the Local Tech Digest MCP server (nk1947-sudo/local-tech-digest-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 →