// MCP TOOL REFERENCE

bridge_tool_request

Execute tools dynamically via bridge

Proxies tool calls to any MCP server

Part of the Mcp Funnel MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

mcp-funnel Execute Risk 5/5

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke bridge_tool_request to trigger processes or run actions in Mcp Funnel. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON BRIDGE_TOOL_REQUEST

bridge_tool_request can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-chris-schra-mcp-funnel.yaml

tools:
  bridge_tool_request:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Mcp Funnel policy for all 21 tools.

// DETAILS

Tool Name bridge_tool_request

Category Execute

MCP Server Mcp Funnel MCP Server

Risk Level High

// MORE MCP FUNNEL TOOLS

Destructive removeData Execute action Execute command Execute force Write version Read alwaysVisibleTools Read args Read defaultPassthroughEnv

View all 21 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like bridge_tool_request have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Agent Passport System — Cryptographic Identity for AI Agents commerce_preflight Agent Passport System — Cryptographic Identity for AI Agents execute_with_context Agent Passport System — Cryptographic Identity for AI Agents gateway_execute_approval Agent Passport System — Cryptographic Identity for AI Agents governance_360 Agent Passport System — Cryptographic Identity for AI Agents parse_governance_block_html AgentClear — API Marketplace for AI Agents call_service

// IN CONTEXT OF HIGH RISK

bridge_tool_request is one of the high-risk operations in Mcp Funnel. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the bridge_tool_request tool do? +

Execute tools dynamically via bridge. It is categorised as a Execute tool in the Mcp Funnel MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bridge_tool_request? +

Add a rule in your Intercept YAML policy under the tools section for bridge_tool_request. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Funnel MCP server.

What risk level is bridge_tool_request? +

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

Can I rate-limit bridge_tool_request? +

Yes. Add a rate_limit block to the bridge_tool_request rule in your Intercept 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 bridge_tool_request completely? +

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

bridge_tool_request is provided by the Mcp Funnel MCP server (mcp-funnel). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

bridge_tool_request

Enforce policies on Mcp Funnel