Fetch a structuredData nodelet or bounded subtree from the current draft.
AI agents call local_draft_get_nodelet to retrieve information from Cascade Cms without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data (a nodelet or subtree) from the current draft without modifying, deleting, or executing any operations. It is a query/fetch operation characteristic of the Read category. The low severity reflects that data retrieval poses minimal risk even if misused by an AI agent, as no mutations or external effects occur.
From the tool's definition Tool name includes 'get' and description states 'Fetch a structuredData nodelet or bounded subtree from the current draft.' Fetching and retrieving data are read-only operations with no side effects.
Attacks that exploit this kind of access
Fetch a structuredData nodelet or bounded subtree from the current draft. It is categorised as a Read tool in the Cascade Cms MCP Server, which means it retrieves data without modifying state.
Register the Cascade Cms MCP server in PolicyLayer and add a rule for local_draft_get_nodelet: 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 Cascade Cms. Nothing to install.
local_draft_get_nodelet 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 local_draft_get_nodelet 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 local_draft_get_nodelet. 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.
local_draft_get_nodelet is provided by the Cascade Cms MCP server (kuklaph/cascade-cms-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 →