AI agents call list_rejection_reasons 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 queries and returns a list of rejection reasons from the recruiting system. It performs a read-only operation without creating, modifying, deleting, or executing any changes to data or external systems. The blast radius of misuse is minimal—an AI agent gaining access would only be able to view organizational configuration data, which poses no data integrity or security risk.
From the tool's definition Tool name 'list_rejection_reasons' and description 'List all rejection reasons configured in the organization' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List all rejection reasons configured in the organization. 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 list_rejection_reasons: 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.
list_rejection_reasons 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 list_rejection_reasons 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 list_rejection_reasons. 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.
list_rejection_reasons 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 →