create_profile
AI agents use create_profile to create or update resources in Mcp Director — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Director environment.
The tool creates new profile configurations (reversible write operation). Severity is medium because misconfiguration of MCP profiles could affect system behavior and available capabilities, but the action is not destructive (profiles can be deleted or updated) and doesn't directly access financial systems or execute arbitrary code.
From the tool's definition Tool name 'create_profile' indicates data creation. Server is a management tool for MCP profiles. Sibling tools include 'delete_profile', 'update_profile', 'apply_profile', confirming this is a profile configuration system where create_profile creates new…
Attacks that exploit this kind of access
create_profile. It is categorised as a Write tool in the Mcp Director MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Director 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 Mcp Director. 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 Mcp Director MCP server (yut0takagi/mcp-director). 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 →