Get documentation for a 4D command. Fetches the documentation from https://developer.4d.com/docs/commands/<command-name> and extracts the article content from the main tag. Results are cached locally for faster subsequent access.
AI agents call get_4d_command_docs to retrieve information from 4D Documentation Viewer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation with no side effects. It queries external documentation and caches results locally, which is a read-only operation. The blast radius if misused by an AI agent is minimal—at worst, it could retrieve large volumes of documentation or spam requests to the 4D documentation server, but no data is modified, deleted, or executed. This is a classic Read category tool.
From the tool's definition Tool fetches documentation content from a remote URL (https://developer.4d.com/docs/commands/<command-name>) and extracts article content.
Attacks that exploit this kind of access
Get documentation for a 4D command. Fetches the documentation from https://developer.4d.com/docs/commands/<command-name> and extracts the article content from the main tag. Results are cached locally for faster subsequent access. It is categorised as a Read tool in the 4D Documentation Viewer MCP Server, which means it retrieves data without modifying state.
Register the 4D Documentation Viewer MCP server in PolicyLayer and add a rule for get_4d_command_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 4D Documentation Viewer. Nothing to install.
get_4d_command_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_4d_command_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_4d_command_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_4d_command_docs is provided by the 4D Documentation Viewer MCP server (mesopelagique/mcp-4d-docs). 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 →