Set a permanent global rule that persists across all projects and sessions
AI agents use set_global_rule to create or update resources in A-Modular-Kingdom — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your A-Modular-Kingdom environment.
This tool modifies system-wide state (global rules) in a reversible manner (rules can typically be updated or removed later). It is Write rather than Execute because it configures behavior rather than triggering external operations. Severity is high because misconfigured global rules could affect all projects and sessions, creating broad impact across the agent's operational environment.
From the tool's definition 'Set a permanent global rule that persists across all projects and sessions' describes creation of configuration data with cross-session durability.
Documented attack patterns abuse exactly the kind of access set_global_rule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and A-Modular-Kingdom, and nothing reaches the server without passing your rules. This is the rule we recommend for set_global_rule:
{
"version": "1",
"default": "deny",
"tools": {
"set_global_rule": {
"limits": [
{
"counter": "set_global_rule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} set_global_rule 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.
Set a permanent global rule that persists across all projects and sessions. It is categorised as a Write tool in the A-Modular-Kingdom MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the A-Modular-Kingdom MCP server in PolicyLayer and add a rule for set_global_rule: 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 A-Modular-Kingdom. Nothing to install.
set_global_rule 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 set_global_rule 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 set_global_rule. 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.
set_global_rule is provided by the A-Modular-Kingdom MCP server (masihmoafi/a-modular-kingdom). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from A-Modular-Kingdom, 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.
14 A-Modular-Kingdom tools catalogued and risk-classified — across an index of 43,000+ MCP servers.