workflow_set_step_deadline
AI agents use workflow_set_step_deadline to create or update resources in Tenzro Ledger MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tenzro Ledger MCP environment.
The name implies a write operation that modifies a deadline attribute on a workflow step. No description is provided, lowering confidence. Based on the server context (wallet, identity, payments, staking), this could affect time-sensitive financial operations, but without more detail, Write at medium severity is the best estimate.
From the tool's definition Tool name 'workflow_set_step_deadline' suggests setting/updating a deadline value on a workflow step.
Attacks that exploit this kind of access
workflow_set_step_deadline. It is categorised as a Write tool in the Tenzro Ledger MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tenzro Ledger MCP server in PolicyLayer and add a rule for workflow_set_step_deadline: 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 Tenzro Ledger MCP. Nothing to install.
workflow_set_step_deadline 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 workflow_set_step_deadline 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 workflow_set_step_deadline. 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.
workflow_set_step_deadline is provided by the Tenzro Ledger MCP server (https://canton-mcp.tenzro.network/mcp). 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 →