Remove a job posting from a portal.
AI agents call unpublish_job_from_portal to permanently remove resources in CATS MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Unpublishing a job from a portal removes its public visibility, which is likely not easily reversible (or requires deliberate re-publishing action). This action could cause candidates to lose access to the job listing and halt recruiting pipelines. The word 'remove' combined with portal publishing context indicates an irreversible or impactful action on external-facing data.
From the tool's definition Remove a job posting from a portal
Attacks that exploit this kind of access
Remove a job posting from a portal. It is categorised as a Destructive tool in the CATS MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for unpublish_job_from_portal: 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 CATS MCP Server. Nothing to install.
unpublish_job_from_portal is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unpublish_job_from_portal 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 unpublish_job_from_portal. 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.
unpublish_job_from_portal is provided by the CATS MCP Server MCP server (vanman2024/cats-mcp-server). 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 →