market_prices
AI agents call market_prices to retrieve information from Tri-Tender Pricing MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Given the empty description, reliance on the tool name alone suggests 'market_prices' retrieves or queries market pricing data for comparison purposes. The broader server context (tender/RFQ pricing, cost calculation, report generation) indicates this tool likely fetches reference market rates rather than modifying data or executing external commands.
From the tool's definition Tool named 'market_prices' with no description provided; contextually appears to be a data retrieval tool within a pricing automation server alongside tools like 'detect_pricing_requirements', 'calculate', and 'render_report'.
Attacks that exploit this kind of access
market_prices. It is categorised as a Read tool in the Tri-Tender Pricing MCP MCP Server, which means it retrieves data without modifying state.
Register the Tri-Tender Pricing MCP server in PolicyLayer and add a rule for market_prices: 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 Tri-Tender Pricing MCP. Nothing to install.
market_prices 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 market_prices 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 market_prices. 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.
market_prices is provided by the Tri-Tender Pricing MCP server (sendsta/tri_tender_pricing_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 →