get_controls
AI agents call get_controls 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 tool name 'get_controls' follows standard naming conventions for read operations (get/fetch/retrieve). In a security posture management platform context, retrieving controls is a non-destructive query operation. The empty description limits confidence slightly, but the verb 'get' is unambiguous for read semantics. No side effects or data mutations are indicated.
From the tool's definition Tool name 'get_controls' indicates a retrieval operation. The description is empty, but the naming pattern combined with sibling tools that are explicitly additive (add_asset, add_evidence, add_functional_test, etc.) strongly suggests this is a query/fetch…
Attacks that exploit this kind of access
get_controls. 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_controls: 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_controls 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_controls 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_controls. 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_controls 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 →