get_page_structure
AI agents call get_page_structure to retrieve information from Amazon Q Web Documentation Reader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve structural information about web pages (DOM structure, hierarchy, layout) to enable documentation navigation. No description provided, but context from sibling tools and server purpose indicates read-only retrieval of page metadata with no side effects or modifications. Classified as Read with medium-high confidence pending explicit description confirmation.
From the tool's definition Tool name 'get_page_structure' combined with sibling tools 'extract_code_examples', 'get_documentation_links', 'read_multiple_docs', 'read_web_documentation' all indicate data retrieval from documentation.
Attacks that exploit this kind of access
get_page_structure. It is categorised as a Read tool in the Amazon Q Web Documentation Reader MCP Server, which means it retrieves data without modifying state.
Register the Amazon Q Web Documentation Reader MCP server in PolicyLayer and add a rule for get_page_structure: 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 Amazon Q Web Documentation Reader. Nothing to install.
get_page_structure 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_page_structure 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_page_structure. 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_page_structure is provided by the Amazon Q Web Documentation Reader MCP server (lumos-labs-hq/amazon-q-docmcp). 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 →