AI agents call find_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 is a read-only search operation that retrieves academic discipline information from the Kula recruiting API. It has no side effects, does not execute code or commands, does not modify data, and does not perform any destructive or financial operations. The narrow scope (searching a reference list of disciplines) further supports a 'low' severity classification, as misuse would only retrieve existing information.
From the tool's definition Tool name 'find_disciplines' and description 'Search academic disciplines (fields of study)' indicate a query/search operation that retrieves data without modifying or executing anything.
Attacks that exploit this kind of access
Search academic disciplines (fields 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 find_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.
find_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 find_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 find_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.
find_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 →