Low Risk

get_documentation

Returns documentation links for Starwind UI

How to control get_documentation ↓

AI agents call get_documentation to retrieve information from Starwind UI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs a read-only operation by returning documentation links. It has no side effects, does not execute code, does not modify data, and does not access financial systems. The blast radius of misuse is negligible since an AI agent retrieving wrong or excessive documentation links causes no harm to systems or data.

From the tool's definition The tool 'Returns documentation links for Starwind UI' — it retrieves and queries documentation references without modifying, executing, or deleting anything.

Documented attack patterns abuse exactly the kind of access get_documentation gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Starwind UI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_documentation:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_documentation": {}
  }
}

get_documentation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Starwind UI MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_documentation tool do? +

Returns documentation links for Starwind UI. It is categorised as a Read tool in the Starwind UI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_documentation? +

Register the Starwind UI MCP Server MCP server in PolicyLayer and add a rule for get_documentation: 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 Starwind UI MCP Server. Nothing to install.

What risk level is get_documentation? +

get_documentation is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_documentation? +

Yes. Add a rate_limit block to the get_documentation 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.

How do I block get_documentation completely? +

Set action: deny in the PolicyLayer policy for get_documentation. 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.

What MCP server provides get_documentation? +

get_documentation is provided by the Starwind UI MCP Server MCP server (starwind-ui/starwind-ui-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Starwind UI MCP Server tool call.

Deterministic rules across all 10 Starwind UI MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

10 Starwind UI MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.