get_model_risk_view
AI agents call get_model_risk_view 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 retrieves or queries a risk model view for analysis purposes with no apparent side effects. While the description is empty, the naming convention and context (security posture platform for threat models) strongly suggest a read operation for generating reports or views. The confidence is lowered from 0.9 to 0.85 due to the lack of explicit description.
From the tool's definition Tool name is 'get_model_risk_view' suggesting retrieval/querying of risk model data. The 'get_' prefix and pattern match sibling 'add_' tools which are write operations, indicating this is the read counterpart.
Attacks that exploit this kind of access
get_model_risk_view. 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_model_risk_view: 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_model_risk_view 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_model_risk_view 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_model_risk_view. 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_model_risk_view 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 →