create_team_role
AI agents use create_team_role to create or update resources in Multilead Open API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Multilead Open API MCP Server environment.
Creating a team role is a reversible data modification action (Write category). The severity is medium because role creation in a team collaboration platform could affect access control and permissions, but the impact depends on what capabilities the role grants. Without a detailed description, confidence is moderated.
From the tool's definition Tool name 'create_team_role' indicates creation of a new role entity. The prefix 'create' aligns with Write category actions that modify data reversibly. The description is empty, limiting direct evidence.
Attacks that exploit this kind of access
create_team_role. It is categorised as a Write tool in the Multilead Open API MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for create_team_role: 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 Multilead Open API MCP Server. Nothing to install.
create_team_role 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_team_role 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_team_role. 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_team_role is provided by the Multilead Open API MCP Server MCP server (vanman2024/multilead-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 →