Analyze a GitHub repository and generate 99 structured AXIS artifacts across 19 programs. Returns snapshot_id plus an artifacts listing; use get_artifact to read files and get_snapshot to re-enumerate outputs without re-running analysis. Requires Authorization: Bearer <api_key>. Use this when the...
Part of the AXIS Toolbox — Agentic Commerce Codebase Intelligence server.
Free to start. No card required.
AI agents call analyze_repo 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_repo 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_repo": {}
}
}See the full AXIS Toolbox — Agentic Commerce Codebase Intelligence policy for all 15 tools.
These attack patterns abuse exactly the kind of access analyze_repo 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 a GitHub repository and generate 99 structured AXIS artifacts across 19 programs. Returns snapshot_id plus an artifacts listing; use get_artifact to read files and get_snapshot to re-enumerate outputs without re-running analysis. Requires Authorization: Bearer <api_key>. Use this when the source of truth is a GitHub repo URL. Pricing: $0.50 standard, $0.15 lite budget mode per repo. This is the paid path for full repo analysis and can return authentication, quota, payment-required, invalid-URL, or GitHub-fetch errors. private repos require a stored GitHub token. Use analyze_files instead for inline file payloads or list_programs/search_and_discover_tools when you are still selecting a workflow.. 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_repo: 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_repo 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_repo 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_repo. 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_repo 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.