Remove a member (assignee) from a card
AI agents use remove_card_member to create or update resources in Superthread Mcp Extended — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Superthread Mcp Extended environment.
Removing a member from a card is a reversible modification — the member can be re-added. It modifies card assignment data but does not delete the card or the user, and has no financial implications. This fits the Write category as it changes existing data in a recoverable way.
From the tool's definition Remove a member (assignee) from a card
Attacks that exploit this kind of access
Remove a member (assignee) from a card. It is categorised as a Write tool in the Superthread Mcp Extended MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Superthread Mcp Extended MCP server in PolicyLayer and add a rule for remove_card_member: 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 Superthread Mcp Extended. Nothing to install.
remove_card_member 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 remove_card_member 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 remove_card_member. 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.
remove_card_member is provided by the Superthread Mcp Extended MCP server (jaey-p/superthread-mcp-extended). 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 →