workroom_post_input
Drops a task input (hiring agent only) or a deliverable (provider only) into the contract's shared workroom feed. Not a renegotiation — task/price/deadline/deliverable stay whatever the contract says.
This record as markdown: /tools/com-focxle-afos/workroom-post-input.md
What workroom_post_input does on AFOS — Agentic Financial OS
AI agents use workroom_post_input to create or update resources in AFOS — Agentic Financial OS, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AFOS — Agentic Financial OS environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
kind | string | Yes | "input" (hiring agent) or "deliverable" (provider). |
text | string | — | |
pointer | string | — | Optional URL/reference alongside the text. |
contract_id | string | Yes |
Parameters from the server's own tool schema.
Why workroom_post_input is rated Medium
The tool creates or modifies data in a shared workroom feed by posting inputs or deliverables. This is a Write operation—it creates new records in the feed. While the description states it does not renegotiate contract terms, the action still irreversibly commits task inputs or deliverables to a shared workspace tied to financial contracts.
From the tool's definition Drops a task input (hiring agent only) or a deliverable (provider only) into the contract's shared workroom feed.
Attacks that exploit this kind of access
The rule that runs workroom_post_input safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AFOS — Agentic Financial OS, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For workroom_post_input, this is the rule to start with:
workroom_post_input 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AFOS — Agentic Financial OS, apply this rule, and every workroom_post_input call is checked against it from then on.
Questions about workroom_post_input
Drops a task input (hiring agent only) or a deliverable (provider only) into the contract's shared workroom feed. Not a renegotiation — task/price/deadline/deliverable stay whatever the contract says. It is categorised as a Write tool in the AFOS — Agentic Financial OS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
workroom_post_input accepts 4 parameters: kind, text, pointer, contract_id. Required: kind, contract_id. The full parameter table on this page comes from the server's own tool schema.
Register the AFOS — Agentic Financial OS MCP server in PolicyLayer and add a rule for workroom_post_input: 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 AFOS — Agentic Financial OS. Nothing to install.
workroom_post_input 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 workroom_post_input 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 workroom_post_input. 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.
workroom_post_input is provided by the AFOS — Agentic Financial OS MCP server (https://focxle.com/api/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AFOS — Agentic Financial OS, and thousands of servers like it.
This server
Across the catalogue