api_save_crypto_profile
Create or replace a signing/encryption profile with a separate configuration-write approval. A profile is a SHARED asset: requests only choose it, so configure it once and bind it with api_bind_crypto_profile. Steps run in array order and order is meaningful: a sign step before the encrypt step s...
This record as markdown: /tools/dutydeck/api-save-crypto-profile.md
What api_save_crypto_profile does on DutyDeck
AI agents use api_save_crypto_profile 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_save_crypto_profile is rated Medium
An AI agent can call api_save_crypto_profile 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_save_crypto_profile 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_save_crypto_profile, this is the rule to start with:
api_save_crypto_profile 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_save_crypto_profile call is checked against it from then on.
Questions about api_save_crypto_profile
Create or replace a signing/encryption profile with a separate configuration-write approval. A profile is a SHARED asset: requests only choose it, so configure it once and bind it with api_bind_crypto_profile. Steps run in array order and order is meaningful: a sign step before the encrypt step signs the plaintext, one after it signs the ciphertext — both patterns exist in real APIs. Allowed algorithms: derive=timestamp-nonce; sign=MD5/SHA1/SHA256/HMAC-SHA1/HMAC-SHA256/SM3; encrypt/decrypt=AES-128-CBC/AES-256-CBC/AES-128-GCM/SM4-CBC. Reference keys by VARIABLE NAME only (keyRef/ivRef) and never put key material in a profile. A sign step needs template + target; encrypt/decrypt act on the whole body and need ivRef. Missing or unfilled keys never block a send: that step is skipped and the run is marked 明文发出. GCM tag placement is P2, so GCM steps are skipped for now. Template placeholders: {{method}} {{path}} {{query}} {{query.sorted}} {{timestamp}} {{nonce}} {{body.raw}} {{body.sha256}} {{body.md5}}. 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_save_crypto_profile: 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_save_crypto_profile 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_save_crypto_profile 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_save_crypto_profile. 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_save_crypto_profile 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