Get detailed description of an OGC Process: required inputs, output format, execution mode.
AI agents call describe_process to retrieve information from SB OGC MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only lookup operation that returns metadata about available processes. It has no side effects—it merely retrieves and presents information about process definitions. This aligns with the 'Read' category for tools that retrieve or query data without side effects.
From the tool's definition Tool description states 'Get detailed description' of a process, which is a query/retrieval operation. The function retrieves metadata about OGC processes (inputs, outputs, execution mode) without modifying or executing anything.
Attacks that exploit this kind of access
Get detailed description of an OGC Process: required inputs, output format, execution mode. It is categorised as a Read tool in the SB OGC MCP MCP Server, which means it retrieves data without modifying state.
Register the SB OGC MCP server in PolicyLayer and add a rule for describe_process: 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.
describe_process is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the describe_process 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 describe_process. 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.
describe_process 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 →