Fetch docs HTML for a component from ui-layouts.com and return as raw_html, plain text, or a main-section snippet.
AI agents call get_docs to retrieve information from Ui Layouts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns documentation in various formats (HTML, plain text, snippets) from ui-layouts.com. It is a pure data retrieval operation with no side effects, matching the 'Read' category definition. The severity is low because fetching documentation poses minimal risk even if misused by an agent — it cannot modify data, execute code, delete resources, or commit financial transactions.
From the tool's definition Tool description explicitly states 'Fetch docs HTML for a component' and 'return as raw_html, plain text, or a main-section snippet' — retrieval operations with no modification, deletion, or execution capabilities.
Documented attack patterns abuse exactly the kind of access get_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ui Layouts, and nothing reaches the server without passing your rules. This is the rule we recommend for get_docs:
{
"version": "1",
"default": "deny",
"tools": {
"get_docs": {}
}
}get_docs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Fetch docs HTML for a component from ui-layouts.com and return as raw_html, plain text, or a main-section snippet. It is categorised as a Read tool in the Ui Layouts MCP Server, which means it retrieves data without modifying state.
Register the Ui Layouts 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 Ui Layouts. 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 Ui Layouts MCP server (ui-layouts/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ui Layouts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Ui Layouts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.