Low Risk

bridge_status

Get JPype bridge status. Shows if the fast bridge mode is active (100-1000x faster than subprocess) or if falling back to subprocess mode.

How to control bridge_status ↓

What bridge_status does on Kawaiidra MCP

AI agents call bridge_status to retrieve information from Kawaiidra MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why bridge_status needs a policy

This tool only retrieves diagnostic information about the bridge mode status (fast bridge vs subprocess fallback). It has no side effects, does not execute code, does not modify data, and does not affect system state. It is purely informational, making it a Read operation with low severity.

From the tool's definition Tool name 'bridge_status' and description 'Get JPype bridge status' — explicitly a retrieval operation that queries the current state of the JPype bridge without modifying or executing anything.

Documented attack patterns abuse exactly the kind of access bridge_status gives an agent:

How to control bridge_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Kawaiidra MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for bridge_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "bridge_status": {}
  }
}

bridge_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Kawaiidra MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about bridge_status

What does the bridge_status tool do? +

Get JPype bridge status. Shows if the fast bridge mode is active (100-1000x faster than subprocess) or if falling back to subprocess mode. It is categorised as a Read tool in the Kawaiidra MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bridge_status? +

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

What risk level is bridge_status? +

bridge_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bridge_status? +

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

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

bridge_status is provided by the Kawaiidra MCP server (wagonbomb/kawaiidra-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kawaiidra MCP tool call.

Start from Kawaiidra MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

94 Kawaiidra MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.