AI agents use create_interview to create or update resources in MCP Ashby Connector — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Ashby Connector environment.
This tool creates new interview records in Ashby's ATS, which is a reversible write operation. While it doesn't read or execute external code, it modifies the system state by adding interview entities. Severity is high because misconfigured interview creation could disrupt hiring workflows, schedule conflicts, or create misleading interview records affecting recruitment decisions.
From the tool's definition Tool name 'create_interview' and description 'Creates a new interview' indicate creation of new data records in the ATS system.
Documented attack patterns abuse exactly the kind of access create_interview 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 create_interview:
{
"version": "1",
"default": "deny",
"tools": {
"create_interview": {
"limits": [
{
"counter": "create_interview_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_interview stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Creates a new interview. It is categorised as a Write tool in the MCP Ashby Connector MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Ashby Connector MCP server in PolicyLayer and add a rule for create_interview: 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.
create_interview is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_interview 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 create_interview. 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.
create_interview 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.