get_static_pages
Read the content of a site's fixed trust pages — Privacy, Terms, Disclaimer (each a list of {heading, paragraphs}) and Contact (an intro). These are real standalone pages (/privacy, /terms, /disclaimer, /contact), not blog posts. Read this before update_static_pages so you can keep the existing s...
This record as markdown: /tools/a3plus-mcp/get-static-pages.md
What get_static_pages does on A3plus
AI agents call get_static_pages to retrieve information from A3plus without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
siteId | string | Yes | The A3Plus site ID. |
Parameters from the server's own tool schema.
Why get_static_pages is rated Low
Even though get_static_pages 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 get_static_pages safely
PolicyLayer is an MCP gateway: it sits between your AI agents and A3plus, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_static_pages, this is the rule to start with:
get_static_pages 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 A3plus, apply this rule, and every get_static_pages call is checked against it from then on.
Questions about get_static_pages
Read the content of a site's fixed trust pages — Privacy, Terms, Disclaimer (each a list of {heading, paragraphs}) and Contact (an intro). These are real standalone pages (/privacy, /terms, /disclaimer, /contact), not blog posts. Read this before update_static_pages so you can keep the existing sections you want. (The About page is read/edited via get_site_content / update_site_content; the FAQ via get_site_faq / update_site_faq.). It is categorised as a Read tool in the A3plus MCP Server, which means it retrieves data without modifying state.
get_static_pages accepts 1 parameter: siteId. Required: siteId. The full parameter table on this page comes from the server's own tool schema.
Register the A3plus MCP server in PolicyLayer and add a rule for get_static_pages: 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 A3plus. Nothing to install.
get_static_pages 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_static_pages 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_static_pages. 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_static_pages is provided by the A3plus MCP server (a3plus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on A3plus, and thousands of servers like it.
This server
Across the catalogue