Publish a job posting to a portal.
AI agents use publish_job_to_portal to create or update resources in CATS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CATS MCP Server environment.
Publishing a job posting creates or modifies publicly-visible data (the job listing on a portal), which is reversible—the posting can be unpublished or edited. This is a Write operation rather than Execute (which would require code/script execution) or Destructive (which cannot be undone).
From the tool's definition Tool name 'publish_job_to_portal' and description 'Publish a job posting to a portal' indicate creation or modification of job postings in an external system.
Attacks that exploit this kind of access
Publish a job posting to a portal. It is categorised as a Write tool in the CATS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CATS MCP Server MCP server in PolicyLayer and add a rule for publish_job_to_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.
publish_job_to_portal 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 publish_job_to_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 publish_job_to_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.
publish_job_to_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 →