Creates a new person with the given name.
AI agents use create_person to create or update resources in MCP Traits Matcher — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Traits Matcher environment.
This tool creates new data (a person record) in the system, which is a reversible write operation. It does not execute code, delete data, move money, or trigger external operations. The severity is low because creating a person record has minimal blast radius—the data can be deleted or modified later, and there are no destructive, financial, or code execution consequences.
From the tool's definition The tool description states it 'Creates a new person' which is a data creation operation. The server context indicates it creates persons with traits in a personality analysis system.
Attacks that exploit this kind of access
Creates a new person with the given name. It is categorised as a Write tool in the MCP Traits Matcher MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Traits Matcher MCP server in PolicyLayer and add a rule for create_person: 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 MCP Traits Matcher. Nothing to install.
create_person 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_person 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_person. 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_person is provided by the MCP Traits Matcher MCP server (waifuai/mcp-traits-matcher). 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 →