Medium Risk

compose_dispenser

Compose a transaction to create, open, or close a dispenser. Dispensers automatically sell tokens for BTC.

Part of the 21e14 server.

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

SECURE 21E14 →

Free to start. No card required.

AI agents use compose_dispenser to create or modify resources in 21e14. 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 compose_dispenser 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 21e14.

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

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

See the full 21e14 policy for all 48 tools.

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

ENFORCE ON MY 21E14 →

View all 48 tools →

These attack patterns abuse exactly the kind of access compose_dispenser 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 compose_dispenser only ever does what you allow.

SECURE 21E14 →

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

What does the compose_dispenser tool do? +

Compose a transaction to create, open, or close a dispenser. Dispensers automatically sell tokens for BTC.. It is categorised as a Write tool in the 21e14 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on compose_dispenser? +

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

What risk level is compose_dispenser? +

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

Can I rate-limit compose_dispenser? +

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

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

compose_dispenser is provided by the 21e14 MCP server (@21e14/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every 21e14 tool call.

Deterministic rules across all 48 21e14 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.