Get full documentation for a specific Griptape Node.
AI agents call get_node_details 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 queries and retrieves existing documentation data from a pre-built SQLite database. It has no side effects, does not modify data, execute code, delete records, or involve financial operations. The blast radius is minimal—an AI agent could retrieve incorrect or irrelevant documentation, but cannot cause harm beyond providing misleading information.
From the tool's definition The tool 'get_node_details' retrieves documentation for a specific Griptape Node. The description uses 'Get', which is a read operation, and the server purpose emphasizes providing 'access to official Griptape framework documentation' without modification…
Documented attack patterns abuse exactly the kind of access get_node_details 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_node_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_node_details": {}
}
}get_node_details 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 full documentation for a specific Griptape Node. 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_node_details: 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_node_details 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_node_details 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_node_details. 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_node_details 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.