Assert structuredData values from the current draft by semantic node selector and target field.
AI agents use local_draft_assert_values to create or update resources in Cascade Cms — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cascade Cms environment.
The term 'assert' in this context means to set or enforce specific values in the structured data of the current draft, which constitutes a write/modify operation on a local draft. It does not delete or execute code, but it does mutate data state. Severity is medium since it affects a local draft (reversible) rather than a published asset.
From the tool's definition 'Assert structuredData values from the current draft' — 'assert' implies setting/writing values into the draft
Attacks that exploit this kind of access
Assert structuredData values from the current draft by semantic node selector and target field. It is categorised as a Write tool in the Cascade Cms MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cascade Cms MCP server in PolicyLayer and add a rule for local_draft_assert_values: 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_assert_values is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the local_draft_assert_values 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_assert_values. 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_assert_values 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 →