Get audit log statistics including total entries and database size.
AI agents call get_audit_log_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.
The tool retrieves and queries audit log statistics (total entries, database size) without performing any side effects, modifications, or system changes. This is a pure data retrieval operation, which falls squarely under the Read category. Severity is low because audit log metadata exposure has minimal direct impact on system security or operations.
From the tool's definition Tool name 'get_audit_log_stats' and description 'Get audit log statistics including total entries and database size' indicate read-only retrieval of audit log metrics with no modification or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_audit_log_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_audit_log_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_audit_log_stats": {}
}
}get_audit_log_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 audit log statistics including total entries and database size. 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_audit_log_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_audit_log_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_audit_log_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_audit_log_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_audit_log_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.