AI agents call get_docs to retrieve information from Ogrid without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Document path (e.g. "features/sorting" or "api/column-def") |
Parameters from the server's own tool schema.
This tool retrieves and queries documentation content by path. It performs a read-only operation with no capability to modify, delete, or execute code. The blast radius is minimal as it only returns existing documentation data. Confidence is high given the clear retrieval semantics in both name and description.
From the tool's definition Tool name 'get_docs' and description 'Get the full content of an OGrid documentation page' indicate retrieval of documentation content without modification or side effects.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Get the full content of an OGrid documentation page by its path. It is categorised as a Read tool in the Ogrid MCP Server, which means it retrieves data without modifying state.
get_docs accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Ogrid MCP server in PolicyLayer and add a rule for get_docs: 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 Ogrid. Nothing to install.
get_docs 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 get_docs 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 get_docs. 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.
get_docs is provided by the Ogrid MCP server (@alaarab/ogrid-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 →