[FacturaHub] Change the role of a team member. Requires admin or owner role.
AI agents use change_member_role to create or update resources in FacturaHub MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FacturaHub MCP Server environment.
This tool modifies a team member's role/permissions, which is a reversible write operation. However, it carries high severity because changing roles can escalate privileges, grant unauthorized access, or revoke admin rights — potentially compromising security and access control for the entire organization.
From the tool's definition Change the role of a team member. Requires admin or owner role.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
[FacturaHub] Change the role of a team member. Requires admin or owner role. It is categorised as a Write tool in the FacturaHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FacturaHub MCP Server MCP server in PolicyLayer and add a rule for change_member_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 FacturaHub MCP Server. Nothing to install.
change_member_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 change_member_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 change_member_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.
change_member_role is provided by the FacturaHub MCP Server MCP server (santy1422/facturahub-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 →