create_entity
Create entity/entities in the project knowledge graph
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/create-entity.md
What create_entity does on Project Guardian MCP
AI agents use create_entity to create or update resources in Project Guardian MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Project Guardian MCP environment.
Why create_entity is rated Medium
This tool creates new entities in a persistent knowledge graph/database. This is a Write operation because it adds data reversibly—entities can be created and later modified or deleted by other tools on the server (delete_entity, delete_observation, delete_relation are siblings).
From the tool's definition The tool description states it will 'Create entity/entities in the project knowledge graph', which is a data creation operation. The server provides 'SQLite database operations' and this tool creates new records in the knowledge graph.
Attacks that exploit this kind of access
The rule that runs create_entity safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_entity, this is the rule to start with:
create_entity 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Project Guardian MCP, apply this rule, and every create_entity call is checked against it from then on.
Questions about create_entity
Create entity/entities in the project knowledge graph. It is categorised as a Write tool in the Project Guardian MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Project Guardian MCP server in PolicyLayer and add a rule for create_entity: 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 Project Guardian MCP. Nothing to install.
create_entity 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_entity 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_entity. 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_entity is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Project Guardian, and thousands of servers like it.
This server
Across the catalogue