Perform an action on a job, such as canceling a running job or clearing job status.
AI agents invoke birst_job_action to trigger actions in Infor Birst MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers operational actions on running jobs (cancel, clear status). Canceling a job is an external operation with side effects that depend on arguments. While canceling a job could be considered destructive to the job's execution, it is reversible in the sense that jobs can typically be restarted; it does not irreversibly delete data.
From the tool's definition 'Perform an action on a job, such as canceling a running job or clearing job status'
Attacks that exploit this kind of access
Perform an action on a job, such as canceling a running job or clearing job status. It is categorised as a Execute tool in the Infor Birst MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Infor Birst MCP Server MCP server in PolicyLayer and add a rule for birst_job_action: 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 Infor Birst MCP Server. Nothing to install.
birst_job_action is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the birst_job_action 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 birst_job_action. 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.
birst_job_action is provided by the Infor Birst MCP Server MCP server (mikahdev/infor-birst-mcp). 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 →