select_tag_compliance_frameworks
AI agents call select_tag_compliance_frameworks 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 verb 'select' typically implies a read/query operation, similar to a SQL SELECT. The tool appears to retrieve or list compliance frameworks associated with a tag. However, the description is empty, which lowers confidence. Given the sibling tools context (threat modeling platform), this likely reads/queries compliance framework data without side effects.
From the tool's definition Tool name 'select_tag_compliance_frameworks' suggests a selection/retrieval operation on compliance framework tags.
Attacks that exploit this kind of access
select_tag_compliance_frameworks. 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 select_tag_compliance_frameworks: 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.
select_tag_compliance_frameworks 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 select_tag_compliance_frameworks 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 select_tag_compliance_frameworks. 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.
select_tag_compliance_frameworks 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 →