set_control_assumption_groups
AI agents use set_control_assumption_groups to create or update resources in Mipiti MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mipiti MCP Server environment.
The 'set' prefix suggests creating or modifying associations between controls and assumption groups within the threat modeling platform. This is reversible data modification (Write category) rather than deletion or execution. Confidence is medium-high due to the empty description and reliance on naming convention analysis alongside server context.
From the tool's definition Tool name 'set_control_assumption_groups' with 'set' verb indicates modification/assignment of control-assumption group relationships. Empty description prevents full certainty.
Attacks that exploit this kind of access
set_control_assumption_groups. It is categorised as a Write tool in the Mipiti MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for set_control_assumption_groups: 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 Mipiti MCP Server. Nothing to install.
set_control_assumption_groups 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 set_control_assumption_groups 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 set_control_assumption_groups. 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.
set_control_assumption_groups is provided by the Mipiti MCP Server MCP server (mipiti/mipiti-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 →