set_action_secret
Set or rotate a secret for an Action. Values are encrypted at rest (libsodium secretbox) and never returned by any endpoint. Used to fill ${UPPERCASE_NAME} placeholders in target_url, header_template, or body_template. Do NOT echo the value back to the user in a conversation — keep it private.
This record as markdown: /tools/deloc-mcp/set-action-secret.md
What set_action_secret does on Deloc
AI agents use set_action_secret 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 set_action_secret is rated Medium
This is a Write operation: it creates or modifies sensitive credential data (secrets) that affect the behavior of downstream Actions. While it does not delete or execute arbitrary code, storing encrypted secrets that control API authentication/authorization is a reversible data modification with significant blast radius if misused (an agent could inject malicious API keys or tokens).
From the tool's definition Tool performs 'Set or rotate a secret' — creates or modifies credential data. Secrets are encrypted at rest and used to fill placeholders in API requests/headers/bodies.
Attacks that exploit this kind of access
The rule that runs set_action_secret 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 set_action_secret, this is the rule to start with:
set_action_secret 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 set_action_secret call is checked against it from then on.
Questions about set_action_secret
Set or rotate a secret for an Action. Values are encrypted at rest (libsodium secretbox) and never returned by any endpoint. Used to fill ${UPPERCASE_NAME} placeholders in target_url, header_template, or body_template. Do NOT echo the value back to the user in a conversation — keep it private. 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 set_action_secret: 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.
set_action_secret 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 set_action_secret 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 set_action_secret. 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.
set_action_secret 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