run_odin_spider_profile · SB OGC MCP: Risk & Policy

WHAT IT DOES

What run_odin_spider_profile does on SB OGC MCP

AI agents invoke run_odin_spider_profile 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_profile needs a policy

The 'run_' prefix combined with context from sibling tools (run_accessibility_map, run_modal_split) suggests this triggers execution of a defined process or model analysis rather than simple data retrieval. While the exact operation is unclear due to the empty description, it almost certainly executes a pre-configured workflow on Dutch mobility/accessibility data.

From the tool's definition Tool name 'run_odin_spider_profile' with 'run_' prefix indicates execution of an operation or analysis on the ODIN model. Similar 'run_' prefixed tools on this server (run_accessibility_map, run_modal_split) execute data processing and analysis workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_odin_spider_profile Rate-limited

run_odin_spider_profile 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_profile": {
      "limits": [
        {
          "counter": "run_odin_spider_profile_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_profile

What does the run_odin_spider_profile tool do? +

run_odin_spider_profile. 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_profile? +

Register the SB OGC MCP server in PolicyLayer and add a rule for run_odin_spider_profile: 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_profile? +

run_odin_spider_profile 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_profile? +

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

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

run_odin_spider_profile 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.