Expands Macroforge macros in TypeScript code and returns the transformed result. Shows: - The fully expanded TypeScript code with all generated methods - Any diagnostics (errors, warnings, info) with line/column locations - Help text for fixing issues (when available) Useful for: - Seeing what co...
AI agents invoke expand-code 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.
This tool executes a code transformation pipeline on user-provided TypeScript code, expanding macros and generating new code. While it returns a result rather than persisting changes, it runs execution logic (macro expansion, code generation) on arbitrary input, placing it in the Execute category.
From the tool's definition 'Expands Macroforge macros in TypeScript code and returns the transformed result' — the tool actively processes and transforms code, running macro expansion logic on arbitrary TypeScript input.
Attacks that exploit this kind of access
Expands Macroforge macros in TypeScript code and returns the transformed result. Shows: - The fully expanded TypeScript code with all generated methods - Any diagnostics (errors, warnings, info) with line/column locations - Help text for fixing issues (when available) Useful for: - Seeing what code the macros generate - Understanding how @derive decorators transform your classes - Debugging macro expansion issues. 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 expand-code: 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.
expand-code 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 expand-code 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 expand-code. 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.
expand-code 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 →