Creates a new governance scope (container for rules and items). Two types:
AI agents use create_scope to create or update resources in Engrams — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Engrams environment.
This tool creates new data structures (governance scopes) within the system, making it a Write operation. It is reversible (scopes can presumably be deleted via the delete_item tool visible in siblings), so it does not qualify as Destructive.
From the tool's definition Tool description states it 'Creates a new governance scope' which is a create operation that modifies the state of the system by adding new containers for rules and items.
Documented attack patterns abuse exactly the kind of access create_scope 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 create_scope:
{
"version": "1",
"default": "deny",
"tools": {
"create_scope": {
"limits": [
{
"counter": "create_scope_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_scope 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.
Free to start. No card required.
Creates a new governance scope (container for rules and items). Two types:. It is categorised as a Write tool in the Engrams MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Engrams MCP server in PolicyLayer and add a rule for create_scope: 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.
create_scope 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 create_scope 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 create_scope. 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.
create_scope 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.