get_sensitivity_ranking
AI agents call get_sensitivity_ranking to retrieve information from ModelRisk MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and '_ranking' suffix suggest this tool fetches pre-computed sensitivity analysis data without modifying state or triggering external operations. Sensitivity rankings are analytical outputs, not data modifications. Low severity because reading analytical results poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_sensitivity_ranking' indicates retrieval of sensitivity analysis results. No description provided, but naming pattern aligns with other Read-category sibling tools (get_active_workbook, get_cell, get_correlation_matrix, get_simulation_results,…
Attacks that exploit this kind of access
get_sensitivity_ranking. It is categorised as a Read tool in the ModelRisk MCP MCP Server, which means it retrieves data without modifying state.
Register the ModelRisk MCP server in PolicyLayer and add a rule for get_sensitivity_ranking: 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 ModelRisk MCP. Nothing to install.
get_sensitivity_ranking 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_sensitivity_ranking 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_sensitivity_ranking. 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_sensitivity_ranking is provided by the ModelRisk MCP server (vosesoftware/modelrisk-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 →