enable_action
Re-enable a disabled or auto-disabled Action. Idempotent.
This record as markdown: /tools/deloc-mcp/enable-action.md
What enable_action does on Deloc
AI agents use enable_action to create or update resources in Deloc, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deloc environment.
Why enable_action is rated Medium
This tool modifies existing data (Action state) reversibly—a disabled Action can be re-disabled if needed. It does not delete data (Destructive), does not execute arbitrary code (Execute), does not involve financial transactions (Financial), and does not merely read data (Read).
From the tool's definition Tool name 'enable_action' and description 'Re-enable a disabled or auto-disabled Action' indicate a state-changing operation that modifies the enabled/disabled status of an Action resource.
Attacks that exploit this kind of access
The rule that runs enable_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deloc, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For enable_action, this is the rule to start with:
enable_action 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 Deloc, apply this rule, and every enable_action call is checked against it from then on.
Questions about enable_action
Re-enable a disabled or auto-disabled Action. Idempotent. It is categorised as a Write tool in the Deloc MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Deloc MCP server in PolicyLayer and add a rule for enable_action: 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 Deloc. Nothing to install.
enable_action 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 enable_action 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 enable_action. 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.
enable_action is provided by the Deloc MCP server (delocdev/deloc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deloc, and thousands of servers like it.
This server
Across the catalogue