AI agents use create_scope to create or update resources in Inoyu Apache Unomi MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Inoyu Apache Unomi MCP Server environment.
This tool creates a new scope object in Apache Unomi, which is a reversible write operation. Scopes in Unomi are configuration entities that define data boundaries and privacy contexts. While creation is a form of data modification, it is reversible (can typically be deleted or disabled) and does not directly execute arbitrary code, delete existing data irreversibly, or move funds.
From the tool's definition Tool name 'create_scope' and description 'Create a new Unomi scope' indicate creation of a new configuration/data object. The verb 'Create' is explicitly stated.
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 Inoyu Apache Unomi MCP Server, 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.
Create a new Unomi scope. It is categorised as a Write tool in the Inoyu Apache Unomi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Inoyu Apache Unomi MCP Server 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 Inoyu Apache Unomi MCP Server. 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 Inoyu Apache Unomi MCP Server MCP server (inoyu-dev/inoyu-mcp-unomi-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Inoyu Apache Unomi MCP Server, 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.
9 Inoyu Apache Unomi MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.