AI agents call get_direct_procurement_details to retrieve information from İhale MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves detailed information about direct procurements from the EKAP v2 portal. No description was provided, but the naming pattern and context of sibling Read-only tools strongly suggest it performs data lookup only. There is no indication of data creation, modification, deletion, code execution, or financial transactions.
From the tool's definition Tool name 'get_direct_procurement_details' indicates data retrieval. Description is empty, but sibling tools on this server (get_ilan_ad_detail, get_recent_tenders, get_tender_details, search_*) are all Read operations that retrieve Turkish procurement data…
Attacks that exploit this kind of access
get_direct_procurement_details. It is categorised as a Read tool in the İhale MCP MCP Server, which means it retrieves data without modifying state.
Register the İhale MCP server in PolicyLayer and add a rule for get_direct_procurement_details: 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 İhale MCP. Nothing to install.
get_direct_procurement_details 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_direct_procurement_details 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_direct_procurement_details. 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_direct_procurement_details is provided by the İhale MCP server (saidsurucu/ihale-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 →