disable_action
Disable an Action so invocations are rejected. Config and secrets are preserved.
This record as markdown: /tools/deloc-mcp/disable-action.md
What disable_action does on Deloc
AI agents use disable_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 disable_action is rated Medium
The tool modifies existing Actions by changing their operational status from enabled to disabled. This is reversible (can be re-enabled) and affects configuration rather than data destruction, making it Write rather than Destructive. Severity is high because disabling Actions in a deployment platform can immediately impact live sites and services accessed by end users, though the operation is recoverable.
From the tool's definition Tool disables an Action, modifying its state by setting invocation rejection while preserving configuration. This is a state change operation that can disrupt live deployments and running services.
Attacks that exploit this kind of access
The rule that runs disable_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 disable_action, this is the rule to start with:
disable_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 disable_action call is checked against it from then on.
Questions about disable_action
Disable an Action so invocations are rejected. Config and secrets are preserved. 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 disable_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.
disable_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 disable_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 disable_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.
disable_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