Low Risk

security_audit

security_audit

How to control security_audit ↓

AI agents call security_audit to retrieve information from Proxima without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Even though security_audit only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Documented attack patterns abuse exactly the kind of access security_audit gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Proxima, and nothing reaches the server without passing your rules. This is the rule we recommend for security_audit:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "security_audit": {}
  }
}

security_audit is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Proxima — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the security_audit tool do? +

security_audit. It is categorised as a Read tool in the Proxima MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on security_audit? +

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

What risk level is security_audit? +

security_audit is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit security_audit? +

Yes. Add a rate_limit block to the security_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 security_audit completely? +

Set action: deny in the PolicyLayer policy for security_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 security_audit? +

security_audit is provided by the Proxima MCP server (zen4-bit/proxima). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Proxima tool call.

Deterministic rules across all 50 Proxima tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

50 Proxima tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.