Import and run an .afmacro file
AI agents invoke affinity_run_macro to trigger actions in Affinity MCP 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 executes external macro files whose behavior is determined by the macro's contents. While not as severe as Destructive (macros could delete files or perform irreversible operations, making this borderline), the primary risk is uncontrolled code execution within the Affinity application context.
From the tool's definition Tool description states 'Import and run an .afmacro file' — the "run" verb indicates execution of arbitrary code/macros.
Attacks that exploit this kind of access
Import and run an .afmacro file. It is categorised as a Execute tool in the Affinity MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Affinity MCP Server MCP server in PolicyLayer and add a rule for affinity_run_macro: 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 Affinity MCP Server. Nothing to install.
affinity_run_macro 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_run_macro 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_run_macro. 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_run_macro is provided by the Affinity MCP Server MCP server (sekharmalla/affinity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →