get_control
AI agents call get_control to retrieve information from Mipiti MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix strongly suggests a read-only query operation that retrieves an existing control definition from the Mipiti platform. No side effects are implied. Even if misused by an agent, retrieving control information poses minimal risk—it cannot modify security configurations, execute code, or cause data loss. Low severity reflects the read-only nature and minimal blast radius.
From the tool's definition Tool name 'get_control' uses the 'get' verb, which conventionally retrieves data without modification. Sibling tools on this server follow a pattern where 'get_*' tools retrieve data (contrasted with 'add_*' tools that create/modify).
Attacks that exploit this kind of access
get_control. It is categorised as a Read tool in the Mipiti MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Mipiti MCP Server MCP server in PolicyLayer and add a rule for get_control: 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.
get_control is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_control 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 get_control. 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.
get_control 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 →