api_declare_variables
Declare variable NAMES on the workspace (shared across all collections) or on one collection, with a separate configuration-write approval. You can only declare name/secret/enabled — you can never write a secret value: do not pass any value, the host stores an empty declaration marked 待填写 and the...
This record as markdown: /tools/dutydeck/api-declare-variables.md
What api_declare_variables does on DutyDeck
AI agents use api_declare_variables to create or update resources in DutyDeck, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DutyDeck environment.
Why api_declare_variables is rated Medium
An AI agent can call api_declare_variables faster than any human can review: one bad instruction and it creates or modifies resources in DutyDeck by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs api_declare_variables safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For api_declare_variables, this is the rule to start with:
api_declare_variables 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 DutyDeck, apply this rule, and every api_declare_variables call is checked against it from then on.
Questions about api_declare_variables
Declare variable NAMES on the workspace (shared across all collections) or on one collection, with a separate configuration-write approval. You can only declare name/secret/enabled — you can never write a secret value: do not pass any value, the host stores an empty declaration marked 待填写 and the human fills it in the 公共配置 panel. Variables that already exist with the same name are left completely untouched (their values are never overwritten by you). Use this to introduce appSecret / aesKey / aesIv before binding a crypto profile, then tell the human which names need values. Use the catalog revision from api_list as expectedRevision. It is categorised as a Write tool in the DutyDeck MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DutyDeck MCP server in PolicyLayer and add a rule for api_declare_variables: 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 DutyDeck. Nothing to install.
api_declare_variables 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 api_declare_variables 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 api_declare_variables. 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.
api_declare_variables is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
This server
Across the catalogue