bec_simulation · Rabi MCP Server MCP: Risk & Policy

WHAT IT DOES

What bec_simulation does on Rabi MCP Server

AI agents invoke bec_simulation to trigger actions in Rabi MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why bec_simulation needs a policy

This tool executes a numerical simulation (solving the Gross-Pitaevskii equation) based on provided physical parameters. It falls under Execute because it runs a computational process whose cost and output depend on arguments. No data is persistently written or deleted; the main concern is computational resource misuse (e.g., very large grids or long simulation times), giving it a medium severity blast radius.

From the tool's definition 'Simulate Bose-Einstein condensate using Gross-Pitaevskii equation' — runs a numerical physics simulation with computational resource usage depending on parameters

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bec_simulation Rate-limited

bec_simulation stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "bec_simulation": {
      "limits": [
        {
          "counter": "bec_simulation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Rabi MCP Server, so you can run agents against it safely.

FAQ

Questions about bec_simulation

What does the bec_simulation tool do? +

Simulate Bose-Einstein condensate using Gross-Pitaevskii equation with realistic physical parameters. It is categorised as a Execute tool in the Rabi MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on bec_simulation? +

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

What risk level is bec_simulation? +

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

Can I rate-limit bec_simulation? +

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

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

bec_simulation is provided by the Rabi MCP Server MCP server (manasp21/rabi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.