# 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.

Agent View of the PolicyLayer registry record for `describe_page_dimensions`. HTML page: https://policylayer.com/tools/com-freebatteryfactory-docs/describe-page-dimensions

## Facts

- Tool: `describe_page_dimensions`
- Server: Docs (`https://freebatteryfactory.com/mcp`) — https://policylayer.com/tools/com-freebatteryfactory-docs.md
- Homepage: https://github.com/https://freebatteryfactory.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "describe_page_dimensions",
    "arguments": {}
  }
}
```

## 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.

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Docs:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "describe_page_dimensions": {}
  }
}
```

## Other tools on Docs (4)

- `get_doc` — Read — https://policylayer.com/tools/com-freebatteryfactory-docs/get-doc.md
- `get_llms_full` — Read — https://policylayer.com/tools/com-freebatteryfactory-docs/get-llms-full.md
- `list_products` — Read — https://policylayer.com/tools/com-freebatteryfactory-docs/list-products.md
- `search_docs` — Read — https://policylayer.com/tools/com-freebatteryfactory-docs/search-docs.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-freebatteryfactory-docs · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-freebatteryfactory-docs