Lists decisions, filtered by tags or ordered by recency. Use when you want to browse/filter decisions by tag or retrieve the N most recent. For keyword search across decision text, use search_decisions_fts instead. For natural-language conceptual search across ALL entity types, use semantic_searc...
AI agents call get_decisions to retrieve information from Engrams without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and queries stored decision records with various filtering and ordering options, returning structured data without modifying, deleting, or executing any external operations. It is purely informational read access to persistent project memory.
From the tool's definition Lists decisions, filtered by tags or ordered by recency. For keyword search across decision text, use search_decisions_fts instead. For natural-language conceptual search across ALL entity types, use semantic_search_engrams.
Documented attack patterns abuse exactly the kind of access get_decisions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Engrams, and nothing reaches the server without passing your rules. This is the rule we recommend for get_decisions:
{
"version": "1",
"default": "deny",
"tools": {
"get_decisions": {}
}
}get_decisions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Lists decisions, filtered by tags or ordered by recency. Use when you want to browse/filter decisions by tag or retrieve the N most recent. For keyword search across decision text, use search_decisions_fts instead. For natural-language conceptual search across ALL entity types, use semantic_search_engrams. For task-relevant context within a token budget, use get_relevant_context. Returns: [{id, summary, rationale, tags, created_at, ...}]. It is categorised as a Read tool in the Engrams MCP Server, which means it retrieves data without modifying state.
Register the Engrams MCP server in PolicyLayer and add a rule for get_decisions: 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 Engrams. Nothing to install.
get_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_decisions 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 get_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_decisions is provided by the Engrams MCP server (stevebrownlee/engrams). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Engrams, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
42 Engrams tools catalogued and risk-classified — across an index of 43,000+ MCP servers.