run_accessibility_map
AI agents invoke run_accessibility_map 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.
The 'run_' prefix and context of other execution tools (run_modal_split, run_odin_profile) strongly suggest this triggers an accessibility map computation/generation process against the OGC API rather than simple data retrieval. This constitutes code or query execution with effects dependent on arguments (map parameters, data selection).
From the tool's definition Tool name 'run_accessibility_map' combined with sibling context showing tools like 'run_modal_split', 'run_odin_compare', 'run_odin_profile' and 'generate_thematic_map' indicates execution of data processing operations.
Attacks that exploit this kind of access
run_accessibility_map. 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.
Register the SB OGC MCP server in PolicyLayer and add a rule for run_accessibility_map: 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.
run_accessibility_map is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_accessibility_map 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.
Set action: deny in the PolicyLayer policy for run_accessibility_map. 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.
run_accessibility_map 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →