AI agents call get_page to retrieve information from Griptape without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to retrieve documentation or code pages from the Griptape knowledge base. The surrounding context (documentation access, code examples, node details) and naming pattern indicate a read operation with no side effects. Even if it queries a database, it returns information without modification or execution.
From the tool's definition Tool name 'get_page' suggests retrieval; sibling tools 'get_code_examples', 'get_node_details', 'search_docs', and 'search_griptape_nodes' are all read-only documentation queries.
Documented attack patterns abuse exactly the kind of access get_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Griptape, and nothing reaches the server without passing your rules. This is the rule we recommend for get_page:
{
"version": "1",
"default": "deny",
"tools": {
"get_page": {}
}
}get_page is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_page. It is categorised as a Read tool in the Griptape MCP Server, which means it retrieves data without modifying state.
Register the Griptape MCP server in PolicyLayer and add a rule for get_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 Griptape. Nothing to install.
get_page 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_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 get_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.
get_page is provided by the Griptape MCP server (kiansalem/griptape-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Griptape, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Griptape tools catalogued and risk-classified — across an index of 43,000+ MCP servers.