Analyze a repository's git commit history and produce structured development knowledge (intents and decisions) for the repo. When to use: - To bootstrap a repository that has no recorded intents/decisions yet. - To extend coverage for new commits since the last run (resumes automatically when no ...
Part of the Kawa Code MCP server.
Free to start. No card required.
AI agents invoke infer_history to trigger processes or run actions in Kawa Code MCP. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
infer_history can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"infer_history": {
"limits": [
{
"counter": "infer_history_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Kawa Code MCP policy for all 21 tools.
These attack patterns abuse exactly the kind of access infer_history gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Analyze a repository's git commit history and produce structured development knowledge (intents and decisions) for the repo. When to use: - To bootstrap a repository that has no recorded intents/decisions yet. - To extend coverage for new commits since the last run (resumes automatically when no commits value is provided). Inputs of note: - estimateOnly (default true): returns a token/cost estimate without running. Call with estimateOnly: true first to preview cost, then re-call with estimateOnly: false to run. - commits (optional): how many recent commits to analyze. Omit to resume from where the last run stopped (or fall back to a sensible default on first run). - commitRange (optional): git revspec selecting a specific window — "sha1..sha2", "branch1..branch2", "sha1^!" for a single commit. Mutually exclusive with commits. Useful for recovering from dropped batches or backfilling specific PRs / branches without re-running the full history. - contextIssues: include PR/MR descriptions and issue discussions when an authenticated forge CLI (gh or glab) is available; auto-skipped otherwise. - allowCommitSplitting: enable when commit history is messy and a single commit may cover unrelated changes. - model, maxStories: Anthropic model and per-run cap. - force (default false): override the re-run guard (see Behavior). Behavior: - A run is asynchronous — returns immediately with a started/pending status; progress is reported separately. - Results are persisted as intents and decisions for the repo on completion. - If interrupted, re-running resumes from where it left off. - Re-run guard: a clean incremental resume runs automatically. But if the repo already has intents and the run cannot cleanly resume (missing/unreachable cursor), or HEAD is not on the default branch, the call STOPS and returns needsDecision instead of running — re-running blind there risks duplicate intents. Present the reason to the user and, if they confirm, re-call with force: true. Run on the default branch (main/master) whenever possible; inferring a feature branch is what force is for. - GitHub and GitLab are supported; the forge is detected from the remote origin.. It is categorised as a Execute tool in the Kawa Code MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kawa Code MCP server in PolicyLayer and add a rule for infer_history: 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 Kawa Code MCP. Nothing to install.
infer_history is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the infer_history 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 infer_history. 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.
infer_history is provided by the Kawa Code MCP server (kawacode-ai/kawa.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Kawa Code MCP 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.