Lists all code bindings attached to a specific Engrams entity (by item_type and item_id). Use to see which files are associated with a decision or pattern. This is entity→files lookup. For the reverse direction (files→entities), use get_context_for_files. Returns: [{id, file_pattern, symbol_patte...
AI agents call get_bindings_for_item 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.
This tool retrieves and queries existing bindings data without modifying, deleting, or executing anything. It is a pure read operation that looks up code bindings associated with an entity. The description emphasizes it is a 'lookup' operation and part of a query workflow. No data is created, modified, deleted, or executed.
From the tool's definition Tool description states "Lists all code bindings attached to a specific Engrams entity" and "Returns: [{id, file_pattern, symbol_pattern, binding_type, confidence, last_verified, ...}]".
Documented attack patterns abuse exactly the kind of access get_bindings_for_item 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_bindings_for_item:
{
"version": "1",
"default": "deny",
"tools": {
"get_bindings_for_item": {}
}
}get_bindings_for_item 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 all code bindings attached to a specific Engrams entity (by item_type and item_id). Use to see which files are associated with a decision or pattern. This is entity→files lookup. For the reverse direction (files→entities), use get_context_for_files. Returns: [{id, file_pattern, symbol_pattern, binding_type, confidence, last_verified, ...}]. Workflow (code binding query): Step 3a of 3 (entity→files direction) — call after bind_code_to_item and verify_bindings have been run. If last_verified is null or stale, call verify_bindings first to confirm globs still match real files. 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_bindings_for_item: 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_bindings_for_item 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_bindings_for_item 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_bindings_for_item. 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_bindings_for_item 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.