record_decision
Re-evaluate an exact intended action and persist an immutable audit decision. This tool cannot override policy or self-approve an action.
This record as markdown: /tools/dev-futur-panda-laguarde/record-decision.md
What record_decision does on Laguarde
AI agents call record_decision to retrieve information from Laguarde without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why record_decision is rated Low
Even though record_decision only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs record_decision safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Laguarde, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For record_decision, this is the rule to start with:
record_decision is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Laguarde, apply this rule, and every record_decision call is checked against it from then on.
Questions about record_decision
Re-evaluate an exact intended action and persist an immutable audit decision. This tool cannot override policy or self-approve an action. It is categorised as a Read tool in the Laguarde MCP Server, which means it retrieves data without modifying state.
Register the Laguarde MCP server in PolicyLayer and add a rule for record_decision: 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 Laguarde. Nothing to install.
record_decision 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 record_decision 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 record_decision. 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.
record_decision is provided by the Laguarde MCP server (laguarde-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Laguarde, and thousands of servers like it.
This server
Across the catalogue