run_odin_spider · SB OGC MCP: Risk & Policy

WHAT IT DOES

What run_odin_spider does on SB OGC MCP

AI agents invoke run_odin_spider to trigger actions in SB OGC MCP. 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 run_odin_spider needs a policy

The 'run_' prefix combined with 'spider' (typically associated with web scraping or automated data collection) indicates this tool executes an external operation whose effects depend on arguments. It is not a simple data retrieval (Read), data modification (Write), or destructive operation.

From the tool's definition Tool name 'run_odin_spider' indicates execution of a process or script (use of 'run'); the sibling tool 'run_accessibility_map' and 'run_modal_split' follow a similar pattern of executing analytical processes on mobility data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_odin_spider Rate-limited

run_odin_spider 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": {
    "run_odin_spider": {
      "limits": [
        {
          "counter": "run_odin_spider_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 SB OGC MCP, so you can run agents against it safely.

FAQ

Questions about run_odin_spider

What does the run_odin_spider tool do? +

run_odin_spider. It is categorised as a Execute tool in the SB OGC MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_odin_spider? +

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

What risk level is run_odin_spider? +

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

Can I rate-limit run_odin_spider? +

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

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

run_odin_spider is provided by the SB OGC MCP server (studio-bereikbaar/sb-ogc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.