describe_page_dimensions
Describe the adaptive dimensions of this site's pages: each named layout regime, the states it can occupy, and the signal and thresholds it is carved from. These are the same boundary definitions that emit the page's @container CSS, so this is the page's real state space rather than a description...
This record as markdown: /tools/com-freebatteryfactory-docs/describe-page-dimensions.md
What describe_page_dimensions does on Docs
AI agents call describe_page_dimensions to retrieve information from Docs without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why describe_page_dimensions is rated Low
Even though describe_page_dimensions only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs describe_page_dimensions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For describe_page_dimensions, this is the rule to start with:
describe_page_dimensions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Docs, apply this rule, and every describe_page_dimensions call is checked against it from then on.
Questions about describe_page_dimensions
Describe the adaptive dimensions of this site's pages: each named layout regime, the states it can occupy, and the signal and thresholds it is carved from. These are the same boundary definitions that emit the page's @container CSS, so this is the page's real state space rather than a description of it. Read-only — no tool here changes the page. Caveat: each dimension's current field is an SSR-time fallback (always the first state), NOT the requesting browser's live state — this manifest is compiled once, server-side, with no viewport to read. HOW to find the live state differs per dimension — some have a data-czap-state DOM attribute to read, some do not and must be derived from viewport width against the stated thresholds instead — so read each dimension's own description rather than assuming one mechanism for all of them. It is categorised as a Read tool in the Docs MCP Server, which means it retrieves data without modifying state.
Register the Docs MCP server in PolicyLayer and add a rule for describe_page_dimensions: 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 Docs. Nothing to install.
describe_page_dimensions 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 describe_page_dimensions 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 describe_page_dimensions. 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.
describe_page_dimensions is provided by the Docs MCP server (https://freebatteryfactory.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docs, and thousands of servers like it.
This server
Across the catalogue