submit_audit · Oathe MCP: Risk & Policy

WHAT IT DOES

What submit_audit does on Oathe

AI agents use submit_audit to create or update resources in Oathe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Oathe environment.

WHY IT NEEDS A POLICY

Why submit_audit needs a policy

This tool creates new audit entries in the oathe.ai security scanning system. While it doesn't modify existing audit data or execute arbitrary code, it does write audit submission records to the platform. The severity is medium because misuse could result in spam submissions or resource exhaustion of the audit service, but it does not irreversibly destroy data, execute code on external systems, or move money.

From the tool's definition Tool description states 'Submit a third-party skill for a behavioral security audit', which creates an audit record in the system. The term 'submit' indicates data creation rather than retrieval or execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_audit Rate-limited

submit_audit stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_audit": {
      "limits": [
        {
          "counter": "submit_audit_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Oathe, so you can run agents against it safely.

FAQ

Questions about submit_audit

What does the submit_audit tool do? +

Submit a third-party skill for a behavioral security audit before installing it. It is categorised as a Write tool in the Oathe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_audit? +

Register the Oathe MCP server in PolicyLayer and add a rule for submit_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 Oathe. Nothing to install.

What risk level is submit_audit? +

submit_audit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit submit_audit? +

Yes. Add a rate_limit block to the submit_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.

How do I block submit_audit completely? +

Set action: deny in the PolicyLayer policy for submit_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.

What MCP server provides submit_audit? +

submit_audit 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.