AI agents use waypath_refresh_page to create or update resources in Waypath — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Waypath environment.
An AI agent can call waypath_refresh_page faster than any human can review — one bad instruction and it creates or modifies resources in Waypath by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
WRITE: rebuild an existing knowledge page against the current store state and update its cached summary/markdown. Use on pages flagged. It is categorised as a Write tool in the Waypath MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Waypath MCP server in PolicyLayer and add a rule for waypath_refresh_page: 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 Waypath. Nothing to install.
waypath_refresh_page 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 waypath_refresh_page 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 waypath_refresh_page. 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.
waypath_refresh_page is provided by the Waypath MCP server (thestack-ai/waypath). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.