Get Visual RAG engine status.
AI agents call get_engine_status to retrieve information from MedVision MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure information retrieval tool—it queries and returns the status of an internal engine component. It has no side effects, does not modify data, does not execute code, and does not delete or move resources. Status checks are read-only operations with minimal blast radius even if misused by an agent, as they cannot alter system state or access sensitive patient data directly.
From the tool's definition Tool name 'get_engine_status' and description 'Get Visual RAG engine status' indicate a query operation that retrieves status information about the RAG engine without modifying any state or triggering external actions.
Attacks that exploit this kind of access
Get Visual RAG engine status. It is categorised as a Read tool in the MedVision MCP MCP Server, which means it retrieves data without modifying state.
Register the MedVision MCP server in PolicyLayer and add a rule for get_engine_status: 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 MedVision MCP. Nothing to install.
get_engine_status 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_engine_status 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_engine_status. 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_engine_status is provided by the MedVision MCP server (u9401066/medvision-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 →