AI agents call search_disciplines to retrieve information from Kula Ai without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries discipline data to support autocomplete functionality. It has no ability to modify, delete, or execute operations. The blast radius of misuse is minimal—an attacker could only enumerate disciplines, which is likely already public information in a recruiting context.
From the tool's definition Tool description explicitly states 'Search academic disciplines by name' and 'Useful for autocompleting field of study'. The verb 'search' and the purpose of autocomplete indicate a read-only query operation with no data modification or side effects.
Attacks that exploit this kind of access
Search academic disciplines by name. Useful for autocompleting field of study. It is categorised as a Read tool in the Kula Ai MCP Server, which means it retrieves data without modifying state.
Register the Kula Ai MCP server in PolicyLayer and add a rule for search_disciplines: 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 Kula Ai. Nothing to install.
search_disciplines 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_disciplines 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_disciplines. 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_disciplines is provided by the Kula Ai MCP server (kula-ai/kula-mcp-server). 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 →