AI agents call get_job_post 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 job posting information from a job board without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing data. The low severity reflects minimal risk even if called inappropriately, as retrieving job post details has no destructive, financial, or operational consequences.
From the tool's definition Tool description states 'Get details of a specific job post' - the verb 'get' and phrase 'details' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get details of a specific job post from the job board. Only use when the user asks about a specific job board listing. 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 get_job_post: 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.
get_job_post 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 get_job_post 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 get_job_post. 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.
get_job_post 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 →