Validates TypeScript code with @derive decorators using Macroforge
AI agents invoke macroforge-autofixer to trigger actions in Macroforge 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.
Validation tools typically parse and execute code analysis against submitted TypeScript source. The 'validate' action implies running code through a processing engine (Macroforge macro expansion/checking), which constitutes executing an external operation. The 'autofixer' suffix suggests it may also modify code, but the description only confirms validation.
From the tool's definition Validates TypeScript code with @derive decorators using Macroforge
Attacks that exploit this kind of access
Validates TypeScript code with @derive decorators using Macroforge. It is categorised as a Execute tool in the Macroforge MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Macroforge MCP Server MCP server in PolicyLayer and add a rule for macroforge-autofixer: 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 Macroforge MCP Server. Nothing to install.
macroforge-autofixer 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 macroforge-autofixer 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 macroforge-autofixer. 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.
macroforge-autofixer is provided by the Macroforge MCP Server MCP server (macroforge-ts/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 →