Execute Affinity Designer automation command / Affinity Designer自動化コマンドを実行
AI agents invoke affinity_execute_command to trigger actions in MCP Affinity Designer Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool runs external commands/automation in Affinity Designer whose effects depend entirely on the arguments passed. While not destructive by default, it can trigger complex workflows, modify documents, export files, or perform other side-effectual operations. An AI agent could abuse this to execute unintended design operations, export sensitive data, or cause uncontrolled document changes.
From the tool's definition Tool name is 'affinity_execute_command' and description states 'Execute Affinity Designer automation command'. The verb 'Execute' combined with 'automation command' indicates arbitrary command execution within Affinity Designer.
Documented attack patterns abuse exactly the kind of access affinity_execute_command gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Affinity Designer Server, and nothing reaches the server without passing your rules. This is the rule we recommend for affinity_execute_command:
{
"version": "1",
"default": "deny",
"tools": {
"affinity_execute_command": {
"limits": [
{
"counter": "affinity_execute_command_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}affinity_execute_command stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Execute Affinity Designer automation command / Affinity Designer自動化コマンドを実行. It is categorised as a Execute tool in the MCP Affinity Designer Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Affinity Designer Server MCP server in PolicyLayer and add a rule for affinity_execute_command: 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 MCP Affinity Designer Server. Nothing to install.
affinity_execute_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the affinity_execute_command 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 affinity_execute_command. 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.
affinity_execute_command is provided by the MCP Affinity Designer Server MCP server (szgk/mcp-affinity-designer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Affinity Designer Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 MCP Affinity Designer Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.