Create a simple user profile with required and optional fields
AI agents use create-profile to create or update resources in Debug Test — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Debug Test environment.
This tool creates user profile data, which is a reversible write operation. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read). Severity is medium because profile creation could affect user data and system state, but the impact is reversible and localized to a single profile record.
From the tool's definition Tool name is 'create-profile' and description states it 'Create a simple user profile with required and optional fields', indicating data creation/modification.
Attacks that exploit this kind of access
Create a simple user profile with required and optional fields. It is categorised as a Write tool in the Debug Test MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Debug Test MCP server in PolicyLayer and add a rule for create-profile: 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 Debug Test. Nothing to install.
create-profile 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-profile 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-profile. 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-profile is provided by the Debug Test MCP server (matsjfunke/debug-test-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 →