Send a Request For Quote to get custom pricing from market makers. Requires authentication.
AI agents use send_rfq to create or update resources in Derive MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Derive MCP environment.
An AI agent can call send_rfq faster than any human can review — one bad instruction and it creates or modifies resources in Derive MCP by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Send a Request For Quote to get custom pricing from market makers. Requires authentication. It is categorised as a Write tool in the Derive MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Derive MCP server in PolicyLayer and add a rule for send_rfq: 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 Derive MCP. Nothing to install.
send_rfq 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 send_rfq 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 send_rfq. 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.
send_rfq is provided by the Derive MCP server (solenyaresearch0000/derive-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 →