Analyze a GitHub repository and generate ${ARTIFACT_COUNT} structured AXIS artifacts across ${PROGRAM_COUNT} 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...
AI agents call analyze_repo to retrieve information from AXIS iliad without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
analyze_repo retrieves and processes repository data to produce deterministic artifacts. It has no side effects on the source repository or external systems—it reads code, analyzes it, and returns results. The tool does not modify, delete, execute code against external services, or trigger deployments (note: 'deploy' is a separate sibling tool). This is purely a read-and-generate analysis operation.
From the tool's definition Tool performs analysis and generates artifacts from a GitHub repository, returning snapshot_id and artifact listings; users then retrieve outputs via get_artifact and get_snapshot.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Analyze a GitHub repository and generate ${ARTIFACT_COUNT} structured AXIS artifacts across ${PROGRAM_COUNT} 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, $25 engineer per repo. Engineer mode (X-Agent-Mode: engineer — Living Architecture) adds a verified LLM specificity pass: a living-architecture.md whose every architectural claim is grounded in the repo. It is categorised as a Read tool in the AXIS iliad MCP Server, which means it retrieves data without modifying state.
Register the AXIS iliad 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 iliad. 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 iliad MCP server (lastmanupinc-hub/axis-iliad). 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 →