update_static_pages
Edit the CONTENT of a site's trust pages for SEO/AEO/GEO. You can change the words; you cannot change the structure (the page set and routes are fixed, no new pages). Pass any subset of privacy/terms/disclaimer/contact — each provided page REPLACES that page's content (read get_static_pages first...
This record as markdown: /tools/a3plus-mcp/update-static-pages.md
What update_static_pages does on A3plus
AI agents use update_static_pages to create or update resources in A3plus, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your A3plus environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
terms | object | — | Terms page: same shape as privacy. |
siteId | string | Yes | The A3Plus site ID. |
contact | object | — | Contact page: { intro: string }. |
privacy | object | — | Privacy page: { sections: [{ heading, paragraphs[] }] } (full list). |
disclaimer | object | — | Disclaimer page: same shape as privacy. |
Parameters from the server's own tool schema.
Why update_static_pages is rated Medium
An AI agent can call update_static_pages faster than any human can review: one bad instruction and it creates or modifies resources in A3plus by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (15 properties)
Attacks that exploit this kind of access
The rule that runs update_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 update_static_pages, this is the rule to start with:
update_static_pages stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 update_static_pages call is checked against it from then on.
Questions about update_static_pages
Edit the CONTENT of a site's trust pages for SEO/AEO/GEO. You can change the words; you cannot change the structure (the page set and routes are fixed, no new pages). Pass any subset of privacy/terms/disclaimer/contact — each provided page REPLACES that page's content (read get_static_pages first to keep existing sections). privacy/terms/disclaimer take { sections: [{ heading, paragraphs[] }] } (≤30 sections, heading ≤200, paragraph ≤5000). contact takes { intro } (≤2000). Takes effect within minutes. It is categorised as a Write tool in the A3plus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_static_pages accepts 5 parameters: terms, siteId, contact, privacy, disclaimer. 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 update_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.
update_static_pages is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_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 update_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.
update_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