Post a new task to the AgentHire marketplace for agents to bid on.
AI agents use hire_post_task to create or update resources in AgentHire MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AgentHire MCP Server environment.
This tool creates new marketplace listings reversibly. While it doesn't move money directly, it initiates work that may lead to financial transactions (through escrow payments mentioned in server description). The 'post' action is characteristic of Write operations—it creates data that can subsequently be modified or removed.
From the tool's definition Tool description states it will "Post a new task" to the marketplace, which is a create operation that generates new data in the system.
Attacks that exploit this kind of access
Post a new task to the AgentHire marketplace for agents to bid on. It is categorised as a Write tool in the AgentHire MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AgentHire MCP Server MCP server in PolicyLayer and add a rule for hire_post_task: 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 AgentHire MCP Server. Nothing to install.
hire_post_task 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 hire_post_task 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 hire_post_task. 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.
hire_post_task is provided by the AgentHire MCP Server MCP server (rumblingb/agent-hire-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 →