AI agents call check_audit_status to retrieve information from Oathe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only tool that retrieves status information about an existing audit. It has no side effects, cannot modify data, and poses minimal security risk. The low blast radius reflects that misuse would only expose audit status metadata, not enable unauthorized modifications or destructive actions.
From the tool's definition Tool queries the status of a previously submitted audit via 'check_audit_status'. Description indicates retrieval only ('Check the status'), with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Check the status of an Oathe security audit submitted via submit_audit. It is categorised as a Read tool in the Oathe MCP Server, which means it retrieves data without modifying state.
Register the Oathe MCP server in PolicyLayer and add a rule for check_audit_status: 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 Oathe. Nothing to install.
check_audit_status 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 check_audit_status 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 check_audit_status. 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.
check_audit_status is provided by the Oathe MCP server (oathe-ai/oathe-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 →