DB에서 상품의 기준 가격을 조회합니다.
AI agents call get_db_price to retrieve information from Price Monitor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads baseline product price data from a database. It performs no modifications, deletions, code execution, or financial transactions. It is a straightforward Read operation with minimal risk—the worst case being information disclosure of internal pricing data.
From the tool's definition Tool description states '상품의 기준 가격을 조회합니다' (retrieves/queries reference price for a product from the database). The name 'get_db_price' and verb 'get' combined with 'query' semantics confirm this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
DB에서 상품의 기준 가격을 조회합니다. It is categorised as a Read tool in the Price Monitor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Price Monitor MCP Server MCP server in PolicyLayer and add a rule for get_db_price: 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 Price Monitor MCP Server. Nothing to install.
get_db_price 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_db_price 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_db_price. 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_db_price is provided by the Price Monitor MCP Server MCP server (moongzee/mcp-price-monitor). 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 →