Skip to main content
Glama
Sign In
MCP Action Firewall

MCP Action Firewall

by starskrime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

firewall_confirm

Confirm a paused high-risk action by submitting the 4-digit approval code. Unlocks execution of blocked tool calls requiring human verification.

Instructions

Call this tool ONLY when the user provides the correct 4-digit approval code to confirm a paused action.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "otp": "<otp>"
    },
    "name": "firewall_confirm"
  }
}

Input Schema

NameRequiredDescriptionDefault
otpYesThe 4-digit code provided by the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses that the tool confirms a paused action but fails to describe side effects, auth requirements, or success/failure behavior. Critical details are missing for a security-related tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that immediately states the tool's purpose and usage condition. No unnecessary words, well front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description should provide more context about what 'paused action' means, prerequisites, and post-conditions. It is insufficient for an agent to correctly invoke the tool in all scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage for parameters is 100%, so baseline is 3. The description mentions the '4-digit approval code', which is similar to the schema's '4-digit code provided by the user', providing no additional meaning beyond what the schema already offers.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to confirm a paused action using a 4-digit approval code. It uses the word 'confirm' as a specific verb and identifies the resource ('paused action'), making it distinct from sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says 'ONLY when the user provides the correct 4-digit approval code', providing clear context for when to use. However, it does not mention what happens on incorrect input or suggest alternative tools for other scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools