This record as markdown: /tools/ashlesh-t-cognirepo/record-decision.md
What record_decision does on CogniRepo
AI agents use record_decision to create or update resources in CogniRepo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CogniRepo environment.
Why record_decision is rated Medium
The tool name implies writing a decision to persistent storage (consistent with the server's purpose of persistent memory and context). No description is provided, which lowers confidence. Based on sibling tools and server context (semantic memory, knowledge graph, session history), this tool most likely creates or modifies a stored record — a Write operation. It does not appear destructive, financial, or executable.
From the tool's definition Tool name 'record_decision' suggests creating/storing a decision record in persistent memory or knowledge graph.
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 CogniRepo, 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 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect CogniRepo, apply this rule, and every record_decision call is checked against it from then on.
Questions about record_decision
record_decision is a write tool on the CogniRepo MCP server. It is categorised as a Write tool in the CogniRepo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CogniRepo 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 CogniRepo. Nothing to install.
record_decision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 CogniRepo MCP server (pypi:cognirepo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on CogniRepo, and thousands of servers like it.
This server
Across the catalogue