AI agents use save_fact 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.
The tool creates or modifies fact data based on its name. Without a description, confidence is reduced, but the naming convention and context (memory/knowledge management server with save/delete operations) strongly suggest a Write operation rather than Read. It is not Destructive (no irreversible deletion), Financial, or Execute (no code execution implied).
From the tool's definition Tool name 'save_fact' indicates data creation/modification. Description is empty, limiting precision. Sibling tools include 'save_memory' and 'delete_memory', suggesting this server manages persistent state. The 'save_' prefix denotes write operations.
Documented attack patterns abuse exactly the kind of access save_fact 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 save_fact:
{
"version": "1",
"default": "deny",
"tools": {
"save_fact": {
"limits": [
{
"counter": "save_fact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} save_fact 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.
save_fact. 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 save_fact: 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.
save_fact 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 save_fact 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 save_fact. 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.
save_fact 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.