Medium Risk

record_decision

Save a structured decision so future clients (or the same client in a future session) can see what was decided and why. Stored in .depwire/decisions.jsonl.

Part of the Depwire Cli server.

record_decision can modify Depwire Cli data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE DEPWIRE CLI →

Free to start. No card required.

AI agents use record_decision to create or modify resources in Depwire Cli. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call record_decision repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Depwire Cli.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "record_decision": {
      "limits": [
        {
          "counter": "record_decision_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Depwire Cli policy for all 23 tools.

Get this rule live on your own Depwire Cli server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY DEPWIRE CLI →

View all 23 tools →

These attack patterns abuse exactly the kind of access record_decision gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so record_decision only ever does what you allow.

SECURE DEPWIRE CLI →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the record_decision tool do? +

Save a structured decision so future clients (or the same client in a future session) can see what was decided and why. Stored in .depwire/decisions.jsonl.. It is categorised as a Write tool in the Depwire Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on record_decision? +

Register the Depwire Cli MCP server in PolicyLayer and add a rule for record_decision: 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 Depwire Cli. Nothing to install.

What risk level is record_decision? +

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

Can I rate-limit record_decision? +

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

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

record_decision is provided by the Depwire Cli MCP server (depwire-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Depwire Cli tool call.

Deterministic rules across all 23 Depwire Cli tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.