Attach an existing Repomix packed output file for AI analysis. This tool accepts either a directory containing a repomix output file or a direct path to a packed repository file. Supports multiple formats: XML (structured with <file> tags), Markdown (human-readable with ## headers and code blocks...
AI agents call attach_packed_output to retrieve information from Repomix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and loads an already-packed repository file into context for analysis. It does not modify, delete, or execute anything — it retrieves existing file content in one of several read-only formats (XML, Markdown, JSON, plain text). The 'refresh' behavior simply re-reads the file if updated, still a read operation. Severity is low as it only reads local files that have already been processed.
From the tool's definition Attach an existing Repomix packed output file for AI analysis
Documented attack patterns abuse exactly the kind of access attach_packed_output gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Repomix, and nothing reaches the server without passing your rules. This is the rule we recommend for attach_packed_output:
{
"version": "1",
"default": "deny",
"tools": {
"attach_packed_output": {}
}
}attach_packed_output 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.
Attach an existing Repomix packed output file for AI analysis. This tool accepts either a directory containing a repomix output file or a direct path to a packed repository file. Supports multiple formats: XML (structured with <file> tags), Markdown (human-readable with ## headers and code blocks), JSON (machine-readable with files as key-value pairs), and Plain text (simple format with separators). Calling the tool again with the same file path will refresh the content if the file has been updated. It will return in that case a new output ID and the updated content. It is categorised as a Read tool in the Repomix MCP Server, which means it retrieves data without modifying state.
Register the Repomix MCP server in PolicyLayer and add a rule for attach_packed_output: 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 Repomix. Nothing to install.
attach_packed_output 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 attach_packed_output 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 attach_packed_output. 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.
attach_packed_output is provided by the Repomix MCP server (yamadashy/repomix). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Repomix tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
8 Repomix tools catalogued and risk-classified — across an index of 42,500+ MCP servers.