Get documentation for Macroforge macros and decorators. Returns information about: - Macro descriptions (e.g., Debug, Serialize, Clone) - Decorator documentation (e.g., @serde, @debug field decorators) - Available macro options and configuration Use without parameters to get the full manifest of ...
AI agents call get-macro-info to retrieve information from Macroforge MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure information retrieval tool that queries and returns documentation metadata about available macros and decorators. It has no side effects—it does not execute code, modify data, delete anything, or trigger external operations. The tool is read-only and serves documentation/discovery purposes.
From the tool's definition Tool retrieves documentation and information about macros and decorators. The description explicitly states it 'Get[s] documentation' and 'Returns information about' macro descriptions and decorator documentation.
Attacks that exploit this kind of access
Get documentation for Macroforge macros and decorators. Returns information about: - Macro descriptions (e.g., Debug, Serialize, Clone) - Decorator documentation (e.g., @serde, @debug field decorators) - Available macro options and configuration Use without parameters to get the full manifest of all available macros and decorators. Use with a name parameter to get info for a specific macro or decorator. It is categorised as a Read tool in the Macroforge MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Macroforge MCP Server MCP server in PolicyLayer and add a rule for get-macro-info: 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.
get-macro-info 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 get-macro-info 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 get-macro-info. 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.
get-macro-info 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 →