Get Affinity Designer application status / Affinity Designerアプリケーションステータスを取得
AI agents call affinity_get_status to retrieve information from MCP Affinity Designer Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves application state/status information only. It has no side effects, creates no resources, executes no commands, and causes no data modifications. It is a pure information-gathering operation, fitting the Read category. The low severity reflects minimal blast radius—even an AI misuse would only expose status data about the running application.
From the tool's definition Tool name 'affinity_get_status' and description 'Get Affinity Designer application status' indicate a query operation that retrieves status information without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access affinity_get_status 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_get_status:
{
"version": "1",
"default": "deny",
"tools": {
"affinity_get_status": {}
}
}affinity_get_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get Affinity Designer application status / Affinity Designerアプリケーションステータスを取得. It is categorised as a Read tool in the MCP Affinity Designer Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Affinity Designer Server MCP server in PolicyLayer and add a rule for affinity_get_status: 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_get_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the affinity_get_status 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_get_status. 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_get_status 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.