application_update · Ashby MCP: Risk & Policy

WHAT IT DOES

What application_update does on Ashby MCP

AI agents use application_update to create or update resources in Ashby MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ashby MCP environment.

WHY IT NEEDS A POLICY

Why application_update needs a policy

This tool modifies application records within the Ashby recruiting system reversibly. Updates to application data (status, notes, assignments, etc.) can be changed again, making it Write rather than Destructive.

From the tool's definition Tool name 'application_update' and description 'Update an application' indicate modification of existing recruiting data without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

application_update Rate-limited

application_update 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "application_update": {
      "limits": [
        {
          "counter": "application_update_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Ashby MCP, so you can run agents against it safely.

FAQ

Questions about application_update

What does the application_update tool do? +

Update an application. It is categorised as a Write tool in the Ashby MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on application_update? +

Register the Ashby MCP server in PolicyLayer and add a rule for application_update: 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 Ashby MCP. Nothing to install.

What risk level is application_update? +

application_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit application_update? +

Yes. Add a rate_limit block to the application_update 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.

How do I block application_update completely? +

Set action: deny in the PolicyLayer policy for application_update. 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.

What MCP server provides application_update? +

application_update is provided by the Ashby MCP server (jaketeagle/ashby-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.