Fetch any JSON value from the current draft by JSON Pointer. Long strings can be sliced with offset and length.
AI agents call local_draft_get_value 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 and queries data from a draft document without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal blast radius—worst case, sensitive data exposure is limited to what's already in the draft.
From the tool's definition Tool name 'local_draft_get_value' and description 'Fetch any JSON value from the current draft by JSON Pointer' indicate data retrieval.
Attacks that exploit this kind of access
Fetch any JSON value from the current draft by JSON Pointer. Long strings can be sliced with offset and length. 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_value: 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_value 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_value 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_value. 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_value 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 →