Lists proposed changes (amendments) to governance scopes, optionally filtered by status (
AI agents call get_scope_amendments 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 lists data about proposed amendments without creating, modifying, deleting, or executing any actions. It is a passive read operation that queries governance scope data. Even in the context of a project memory system managing decisions and patterns, listing amendments poses minimal risk as it only surfaces information without side effects.
From the tool's definition Tool name is 'get_scope_amendments' and description states 'Lists proposed changes (amendments) to governance scopes' — this is a retrieval/query operation with no modification capability.
Documented attack patterns abuse exactly the kind of access get_scope_amendments 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_scope_amendments:
{
"version": "1",
"default": "deny",
"tools": {
"get_scope_amendments": {}
}
}get_scope_amendments 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 proposed changes (amendments) to governance scopes, optionally filtered by status (. 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_scope_amendments: 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_scope_amendments 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_scope_amendments 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_scope_amendments. 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_scope_amendments 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.