audit-device-enable · Vault MCP Server (mschuchard) MCP

WHAT IT DOES

What audit-device-enable does on Vault MCP Server (mschuchard)

AI agents use audit-device-enable to create or update resources in Vault MCP Server (mschuchard) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vault MCP Server (mschuchard) environment.

WHY IT NEEDS A POLICY

Why audit-device-enable needs a policy

Based on the tool name and sibling tool 'audit-device-disable', this tool likely enables an audit device in HashiCorp Vault, which is a write/configuration operation that mounts a new audit backend. This is reversible (it can be disabled). Confidence is lowered due to empty description.

From the tool's definition Tool name 'audit-device-enable' and server context of managing audit devices in HashiCorp Vault. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

audit-device-enable Rate-limited

audit-device-enable 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": {
    "audit-device-enable": {
      "limits": [
        {
          "counter": "audit-device-enable_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 Vault MCP Server (mschuchard), so you can run agents against it safely.

FAQ

Questions about audit-device-enable

What does the audit-device-enable tool do? +

audit-device-enable. It is categorised as a Write tool in the Vault MCP Server (mschuchard) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on audit-device-enable? +

Register the Vault MCP Server (mschuchard) MCP server in PolicyLayer and add a rule for audit-device-enable: 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 Vault MCP Server (mschuchard). Nothing to install.

What risk level is audit-device-enable? +

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

Can I rate-limit audit-device-enable? +

Yes. Add a rate_limit block to the audit-device-enable 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 audit-device-enable completely? +

Set action: deny in the PolicyLayer policy for audit-device-enable. 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 audit-device-enable? +

audit-device-enable is provided by the Vault MCP Server (mschuchard) MCP server (mschuchard/vault-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.