AI agents call search_programs to retrieve information from YOKATLAS API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool operates within a data-querying interface (YOKATLAS API MCP Server) for higher education information. Despite lacking an explicit description, the naming and context of sibling list/search tools strongly indicate it performs read-only queries on public educational data with no side effects or capability to modify state. Confidence is moderate (0.75) rather than high due to the empty description.
From the tool's definition Tool named 'search_programs' with no description; context indicates it retrieves 'details about undergraduate and associate degree programs in Turkey' alongside sibling tools 'list_cities', 'list_program_groups', 'list_universities', all of which are data…
Documented attack patterns abuse exactly the kind of access search_programs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and YOKATLAS API MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_programs:
{
"version": "1",
"default": "deny",
"tools": {
"search_programs": {}
}
}search_programs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_programs. It is categorised as a Read tool in the YOKATLAS API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the YOKATLAS API MCP Server MCP server in PolicyLayer and add a rule for search_programs: 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 YOKATLAS API MCP Server. Nothing to install.
search_programs 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_programs 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_programs. 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_programs is provided by the YOKATLAS API MCP Server MCP server (saidsurucu/yokatlas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 YOKATLAS API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 YOKATLAS API MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.