create_offer
AI agents use create_offer to create or update resources in Invoice Agent MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Invoice Agent MCP Server environment.
The tool creates new offer documents (write operation). Severity is medium because offers are business-critical documents that establish contractual obligations and could be issued incorrectly if misused by an AI agent, but the operation is reversible (offers can be corrected/replaced).
From the tool's definition Tool name 'create_offer' combined with server purpose (invoice creation via natural language) and sibling tools (create_invoice, get_invoice_status, list_invoices) indicates this creates or generates offer documents, which are reversible data modifications.
Attacks that exploit this kind of access
create_offer. It is categorised as a Write tool in the Invoice Agent MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Invoice Agent MCP Server MCP server in PolicyLayer and add a rule for create_offer: 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 Invoice Agent MCP Server. Nothing to install.
create_offer 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 create_offer 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 create_offer. 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.
create_offer is provided by the Invoice Agent MCP Server MCP server (samabdelkhalek-code/invoice-agent-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 →