Get all decisions recorded for a project across all intents. Use this to review the project's decision history: - See what architectural decisions have been made - Understand past trade-offs and their rationale - Find decisions affecting specific files - Review constraint violations that were av...
Part of the Kawa Code MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_project_decisions to retrieve information from Kawa Code MCP 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 get_project_decisions 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.
tools:
get_project_decisions:
rules:
- action: allowSee the full Kawa Code MCP policy for all 17 tools.
Agents calling read-class tools like get_project_decisions have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get all decisions recorded for a project across all intents. Use this to review the project's decision history: - See what architectural decisions have been made - Understand past trade-offs and their rationale - Find decisions affecting specific files - Review constraint violations that were avoided Returns: - decisions: Array of decisions with their intent context - count: Total number of decisions Each decision includes: - intentId: The intent this decision belongs to - type: fork, abandoned, discovery, constraint, tradeoff, or dependency - summary: Brief description of the decision - rationale: Why this decision was made - relatedFiles: Files affected by this decision - constraintViolations: Options that were rejected due to constraints. It is categorised as a Read tool in the Kawa Code MCP MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_project_decisions. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kawa Code MCP MCP server.
get_project_decisions 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 get_project_decisions rule in your Intercept 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 Intercept policy for get_project_decisions. 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.
get_project_decisions is provided by the Kawa Code MCP MCP server (@kawacode/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept