AI agents call search_jobs to retrieve information from MCP Ashby Connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a search operation which is fundamentally a read-only action that queries existing job data. No creation, modification, deletion, or execution of external operations is described. The blast radius of misuse is minimal—an agent could retrieve unintended job listings but cannot alter hiring data or cause harm through information retrieval alone.
From the tool's definition Tool name 'search_jobs' and description 'Search for jobs by title and filters' indicate a query operation that retrieves job records without modifying or deleting data.
Documented attack patterns abuse exactly the kind of access search_jobs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Ashby Connector, and nothing reaches the server without passing your rules. This is the rule we recommend for search_jobs:
{
"version": "1",
"default": "deny",
"tools": {
"search_jobs": {}
}
}search_jobs 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 for jobs by title and filters. It is categorised as a Read tool in the MCP Ashby Connector MCP Server, which means it retrieves data without modifying state.
Register the MCP Ashby Connector MCP server in PolicyLayer and add a rule for search_jobs: 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 MCP Ashby Connector. Nothing to install.
search_jobs 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_jobs 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_jobs. 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_jobs is provided by the MCP Ashby Connector MCP server (thnico/mcp-ashby). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Ashby Connector, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 MCP Ashby Connector tools catalogued and risk-classified — across an index of 43,000+ MCP servers.