AI agents call pageGet to retrieve information from Routine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves page data without side effects. It is a simple Read operation that queries existing information from the Routine platform, posing minimal security risk even if called inappropriately by an agent.
From the tool's definition Tool description states 'Get a page' with no modification, deletion, or execution capability implied. The verb 'Get' indicates data retrieval.
Attacks that exploit this kind of access
Get a page. It is categorised as a Read tool in the Routine MCP Server, which means it retrieves data without modifying state.
Register the Routine MCP server in PolicyLayer and add a rule for pageGet: 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 Routine. Nothing to install.
pageGet 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 pageGet 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 pageGet. 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.
pageGet is provided by the Routine MCP server (routineco/mcp-server). 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 →