Analyze source files directly and generate the full 99-artifact AXIS bundle without using GitHub. Returns snapshot_id plus artifact listing; use this for local, generated, or unsaved code. Requires Authorization: Bearer <api_key>. Use analyze_repo for GitHub URLs or improve_my_agent_with_axis for...
Risk signalsAccepts file system path (files[].path) · Accepts raw HTML/template content (files[].content)
Part of the AXIS Toolbox — Agentic Commerce Codebase Intelligence server.
Free to start. No card required.
AI agents call analyze_files to retrieve information from AXIS Toolbox — Agentic Commerce Codebase Intelligence without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though analyze_files only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"analyze_files": {}
}
}See the full AXIS Toolbox — Agentic Commerce Codebase Intelligence policy for all 15 tools.
These attack patterns abuse exactly the kind of access analyze_files gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Analyze source files directly and generate the full 99-artifact AXIS bundle without using GitHub. Returns snapshot_id plus artifact listing; use this for local, generated, or unsaved code. Requires Authorization: Bearer <api_key>. Use analyze_repo for GitHub URLs or improve_my_agent_with_axis for recommendation-first agent hardening.. It is categorised as a Read tool in the AXIS Toolbox — Agentic Commerce Codebase Intelligence MCP Server, which means it retrieves data without modifying state.
Register the AXIS Toolbox — Agentic Commerce Codebase Intelligence MCP server in PolicyLayer and add a rule for analyze_files: 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 AXIS Toolbox — Agentic Commerce Codebase Intelligence. Nothing to install.
analyze_files 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 analyze_files 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 analyze_files. 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.
analyze_files is provided by the AXIS Toolbox — Agentic Commerce Codebase Intelligence MCP server (https://axis-api-6c7z.onrender.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 AXIS Toolbox — Agentic Commerce Codebase Intelligence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.