Crea un nuevo usuario con nombre, apellido y DNI
AI agents use crear-usuario to create or update resources in MCP API Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP API Server environment.
This tool creates a new user entity in the system with personally identifiable information (name, surname, DNI). It is a Write operation as it adds new data reversibly. Medium severity because it involves PII and could be misused to create unauthorized accounts, but is not irreversible or financial.
From the tool's definition 'Crea un nuevo usuario con nombre, apellido y DNI' — creates a new user record with personal data
Attacks that exploit this kind of access
Crea un nuevo usuario con nombre, apellido y DNI. It is categorised as a Write tool in the MCP API Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP API Server MCP server in PolicyLayer and add a rule for crear-usuario: 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 API Server. Nothing to install.
crear-usuario 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 crear-usuario 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 crear-usuario. 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.
crear-usuario is provided by the MCP API Server MCP server (mcgiverdev/mcp-api-v1). 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 →