start_security_audit · Claude Team MCP: Risk & Policy

WHAT IT DOES

What start_security_audit does on Claude Team MCP

AI agents invoke start_security_audit to trigger actions in Claude Team MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why start_security_audit needs a policy

A security audit tool triggers an external operation (audit scanning/analysis) whose effects and scope depend on arguments and system state. This is Execute rather than Read because it initiates active processes that may modify logging, generate reports, or trigger remediation workflows. Severity is high because misconfiguration or targeting wrong codebases could expose sensitive findings or halt development.

From the tool's definition Tool name 'start_security_audit' indicates it initiates an automated security audit process. The server description emphasizes the team 'audits security' as a core capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

start_security_audit Rate-limited

start_security_audit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_security_audit": {
      "limits": [
        {
          "counter": "start_security_audit_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about start_security_audit

What does the start_security_audit tool do? +

start_security_audit. It is categorised as a Execute tool in the Claude Team MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_security_audit? +

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

What risk level is start_security_audit? +

start_security_audit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_security_audit? +

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

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

start_security_audit is provided by the Claude Team MCP server (lakshan12367/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.