AI agents call get_equipment_status to retrieve information from Vanam Erp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves/queries existing equipment PM status data with no side effects. It fits the 'Read' category as it performs a simple data lookup operation typical of inventory/asset management systems. The low severity reflects minimal blast radius—an AI agent misusing this tool would only access status information, not modify or delete anything.
From the tool's definition Tool name 'get_equipment_status' and description '전체 장비의 점검(PM) 현황을 조회한다' (retrieves equipment inspection status) indicate a query operation. The description states 'No arguments required' and the tool retrieves current PM status without modifying data.
Attacks that exploit this kind of access
전체 장비의 점검(PM) 현황을 조회한다. 인자가 필요 없다. 예:. It is categorised as a Read tool in the Vanam Erp MCP Server, which means it retrieves data without modifying state.
Register the Vanam Erp MCP server in PolicyLayer and add a rule for get_equipment_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 Vanam Erp. Nothing to install.
get_equipment_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_equipment_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_equipment_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_equipment_status is provided by the Vanam Erp MCP server (leejunheon/vanam-erp-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 →