AI agents use create_application 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 a new application record in the Ashby ATS, which is a reversible write operation. It modifies the system state by adding data but does not delete, destroy, or execute arbitrary code.
From the tool's definition Tool is named 'create_application' and described as 'Creates a new application'. This creates a new record in an ATS system without deleting or modifying existing data.
Documented attack patterns abuse exactly the kind of access create_application 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_application:
{
"version": "1",
"default": "deny",
"tools": {
"create_application": {
"limits": [
{
"counter": "create_application_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_application 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 application. 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_application: 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_application 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_application 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_application. 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_application 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.