Publish a page by its ID
AI agents use publishPage to create or update resources in GROWI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GROWI MCP Server environment.
Publishing a page changes its metadata/status (from draft/unpublished to published) reversibly—it can be unpublished again. This is a modification operation but not destructive (data is not deleted or permanently overwritten). The blast radius is medium because publishing could expose wiki content to unintended audiences if the wrong page ID is targeted, but the operation is reversible.
From the tool's definition Tool description: 'Publish a page by its ID'. The verb 'publish' indicates a state change operation that modifies a page's visibility or status, making it a write operation.
Attacks that exploit this kind of access
Publish a page by its ID. It is categorised as a Write tool in the GROWI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GROWI MCP Server MCP server in PolicyLayer and add a rule for publishPage: 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 GROWI MCP Server. Nothing to install.
publishPage 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 publishPage 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 publishPage. 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.
publishPage is provided by the GROWI MCP Server MCP server (mechanicalgirldev/growi-mcp-server-web). 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 →