Start Affinity Designer application / Affinity Designerアプリケーションを開始
AI agents invoke affinity_start_app 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.
Starting an application is an Execute action: it triggers an external process whose downstream effects are determined by what the agent does with the running application (as evidenced by sibling tools like affinity_apply_effect, affinity_delete_layer, affinity_close_document).
From the tool's definition Tool description states 'Start Affinity Designer application' — this launches an external application, which is an external operation whose effects depend on system state and subsequent user/agent actions.
Documented attack patterns abuse exactly the kind of access affinity_start_app 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_start_app:
{
"version": "1",
"default": "deny",
"tools": {
"affinity_start_app": {
"limits": [
{
"counter": "affinity_start_app_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}affinity_start_app 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.
Start Affinity Designer application / 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_start_app: 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_start_app 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_start_app 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_start_app. 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_start_app 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.