View and search the command audit log. All omniwire_exec calls are automatically logged. Supports viewing recent entries, filtering, and computing stats.
AI agents call omniwire_audit to retrieve information from OmniWire without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing audit log data without side effects. The verbs 'view', 'search', 'filter', and 'computing stats' are all informational read operations. While the server manages infrastructure and commands, this specific tool only inspects historical logs rather than executing commands, modifying data, or deleting records.
From the tool's definition Tool description states 'View and search the command audit log' with support for 'viewing recent entries, filtering, and computing stats' — all read-only operations with no mention of modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access omniwire_audit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OmniWire, and nothing reaches the server without passing your rules. This is the rule we recommend for omniwire_audit:
{
"version": "1",
"default": "deny",
"tools": {
"omniwire_audit": {}
}
}omniwire_audit 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.
View and search the command audit log. All omniwire_exec calls are automatically logged. Supports viewing recent entries, filtering, and computing stats. It is categorised as a Read tool in the OmniWire MCP Server, which means it retrieves data without modifying state.
Register the OmniWire MCP server in PolicyLayer and add a rule for omniwire_audit: 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 OmniWire. Nothing to install.
omniwire_audit 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 omniwire_audit 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 omniwire_audit. 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.
omniwire_audit is provided by the OmniWire MCP server (voidchecksum/omniwire). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OmniWire, 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.
88 OmniWire tools catalogued and risk-classified — across an index of 43,000+ MCP servers.