AI agents call search_kvkk_decisions to retrieve information from Yargı MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a legal database to retrieve existing court decisions on data protection matters. It retrieves or queries data with no side effects, reversible modifications, code execution, destructive operations, or financial transactions. The tool is read-only access to published legal documents.
From the tool's definition Tool name includes 'search' and description states 'searching Turkish data protection decisions' with use cases limited to reviewing 'privacy, consent, and data breach cases' — all retrieval operations with no modification, deletion, or execution of external…
Attacks that exploit this kind of access
Use this when searching Turkish data protection (KVKK/GDPR equivalent) decisions. For privacy, consent, and data breach cases. It is categorised as a Read tool in the Yargı MCP MCP Server, which means it retrieves data without modifying state.
Register the Yargı MCP server in PolicyLayer and add a rule for search_kvkk_decisions: 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 Yargı MCP. Nothing to install.
search_kvkk_decisions 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_kvkk_decisions 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_kvkk_decisions. 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_kvkk_decisions is provided by the Yargı MCP server (saidsurucu/yargi-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 →