add_sequence_step
Add a step to an existing sequence. Steps are executed in order with configurable delays between them. Enterprise only.
This record as markdown: /tools/adrata-adrata-mcp/add-sequence-step.md
What add_sequence_step does on Adrata
AI agents use add_sequence_step to create or update resources in Adrata, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adrata environment.
Why add_sequence_step is rated Medium
An AI agent can call add_sequence_step faster than any human can review: one bad instruction and it creates or modifies resources in Adrata by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs add_sequence_step safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adrata, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_sequence_step, this is the rule to start with:
add_sequence_step stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Adrata, apply this rule, and every add_sequence_step call is checked against it from then on.
Questions about add_sequence_step
Add a step to an existing sequence. Steps are executed in order with configurable delays between them. Enterprise only. It is categorised as a Write tool in the Adrata MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Adrata MCP server in PolicyLayer and add a rule for add_sequence_step: 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 Adrata. Nothing to install.
add_sequence_step 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 add_sequence_step 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 add_sequence_step. 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.
add_sequence_step is provided by the Adrata MCP server (@adrata/adrata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adrata, and thousands of servers like it.
This server
Across the catalogue