Get tool usage statistics including call counts, error rates, and hourly distribution.
AI agents call get_usage_stats to retrieve information from OODA Computer Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical statistics and metrics about tool usage. It performs a data query operation that does not modify, execute code, delete data, or move money. The read-only nature of querying usage statistics with no capability to alter system state or trigger external actions places it clearly in the Read category with low severity.
From the tool's definition Tool name 'get_usage_stats' and description 'Get tool usage statistics including call counts, error rates, and hourly distribution' indicate retrieval of monitoring data with no side effects.
Documented attack patterns abuse exactly the kind of access get_usage_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for get_usage_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_usage_stats": {}
}
}get_usage_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get tool usage statistics including call counts, error rates, and hourly distribution. It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.
Register the OODA Computer Control MCP server in PolicyLayer and add a rule for get_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 OODA Computer Control. Nothing to install.
get_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_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_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_usage_stats is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.