get_documentation_page
AI agents call get_documentation_page to retrieve information from UAB Research Computing Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries documentation pages with no ability to modify, delete, or execute operations. The lack of side effects and the server's purpose as a documentation provider confirm this is a Read category tool. Severity is low because documentation access poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_documentation_page' indicates retrieval of documentation content. Server context describes 'search and retrieve information' about HPC cluster documentation.
Attacks that exploit this kind of access
get_documentation_page. It is categorised as a Read tool in the UAB Research Computing Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UAB Research Computing Documentation MCP Server MCP server in PolicyLayer and add a rule for get_documentation_page: 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 UAB Research Computing Documentation MCP Server. Nothing to install.
get_documentation_page 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_documentation_page 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_documentation_page. 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_documentation_page is provided by the UAB Research Computing Documentation MCP Server MCP server (jgordini/rcmcp). 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 →