Retrieve and summarize usage statistics for the local LLM MCP server.
AI agents call get_local_llm_usage_stats to retrieve information from Local Llm Delegation without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves usage statistics—a passive information gathering operation with no side effects, no code execution, no data modification, and no destructive capabilities. It falls squarely into the Read category with low severity since access to usage statistics presents minimal risk to system integrity or operations.
From the tool's definition The tool name contains 'get' and the description states 'Retrieve and summarize usage statistics', indicating a read-only operation that queries existing data without modification or execution.
Attacks that exploit this kind of access
Retrieve and summarize usage statistics for the local LLM MCP server. It is categorised as a Read tool in the Local Llm Delegation MCP Server, which means it retrieves data without modifying state.
Register the Local Llm Delegation MCP server in PolicyLayer and add a rule for get_local_llm_usage_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 Llm Delegation. Nothing to install.
get_local_llm_usage_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_local_llm_usage_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_local_llm_usage_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_local_llm_usage_stats is provided by the Local Llm Delegation MCP server (mrrodriguez/local-llm-delegation-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 →