add_fact
AI agents use add_fact to create or update resources in Pyke MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pyke MCP Server environment.
This tool adds facts to a logic programming knowledge base, which is a Create operation—modifying state reversibly. It does not execute arbitrary code, delete data irreversibly, move money, or have financial impact. The empty description lowers confidence slightly, but the name and context of sibling tools clearly indicate a Write operation.
From the tool's definition Tool name is 'add_fact' which indicates creating/adding data to a knowledge base. Sibling tools include 'add_rule', 'add_facts_and_rules', and 'clear_program', confirming this server manages mutable logical program state.
Attacks that exploit this kind of access
add_fact. It is categorised as a Write tool in the Pyke MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pyke MCP Server MCP server in PolicyLayer and add a rule for add_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 Pyke MCP Server. Nothing to install.
add_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 add_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 add_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.
add_fact is provided by the Pyke MCP Server MCP server (newjerseystyle/pyke-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →