Args:
AI agents call search_medicines to retrieve information from Maharashtra Medicine MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations retrieve or query data without modifying, deleting, or executing code. This is a classic Read operation. The blast radius is minimal—searching medicine inventory data poses no risk of data loss, financial impact, or unauthorized execution. Low severity is appropriate for a read-only query tool.
From the tool's definition The tool is named 'search_medicines' and belongs to a server described as providing tools for 'inventory searching, expiry tracking, and supplier or buyer performance analysis.' The function arguments are not detailed, but the name and context indicate this…
Attacks that exploit this kind of access
Args:. It is categorised as a Read tool in the Maharashtra Medicine MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Maharashtra Medicine MCP Server MCP server in PolicyLayer and add a rule for search_medicines: 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 Maharashtra Medicine MCP Server. Nothing to install.
search_medicines 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 search_medicines 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 search_medicines. 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.
search_medicines is provided by the Maharashtra Medicine MCP Server MCP server (rajendraprasad96536/inventory-mcp-server). 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 →