submit_machining_rfq
Submit a structured machining/testing RFQ. Runs a lightweight compliance screen (prohibited-use + sanctions) and, if cleared, registers the enquiry for human follow-up from enquiry@feode.com. Not a contract or quotation; no payment is taken here. You must provide the legal entity behind the request.
This record as markdown: /tools/com-feode-feode-mcp/submit-machining-rfq.md
What submit_machining_rfq does on Feode Mcp
AI agents use submit_machining_rfq to create or update resources in Feode Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Feode Mcp environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Contact email |
notes | string | — | Any other details (optional) |
company | string | Yes | Legal entity name placing the order |
country | string | Yes | Country of registration of the legal entity |
end_use | string | Yes | Declared end-use of the part |
industry | string | — | Industry sector |
material | string | Yes | Material / grade |
quantity | string | Yes | Quantity |
tolerance | string | — | Key tolerances (optional) |
drawing_url | string | — | Link to drawing/spec if available (optional) |
contact_name | string | Yes | Real human contact name |
part_description | string | Yes | Part/component description or drawing reference |
Parameters from the server's own tool schema.
Why submit_machining_rfq is rated Medium
This tool creates/writes a new data record (an RFQ/enquiry) in the system for processing, making it a Write operation. Severity is medium because: (1) it does not execute external transactions or modify existing critical data; (2) it includes built-in compliance screening (prohibited-use, sanctions checks) that mitigates misuse; (3) the impact is limited to initiating a business inquiry that requires human review…
From the tool's definition Tool 'submit_machining_rfq' creates a new request record ('registers the enquiry') that requires human follow-up. It performs a state change in the backend system by adding a new RFQ entry.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs submit_machining_rfq safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Feode Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For submit_machining_rfq, this is the rule to start with:
submit_machining_rfq 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 Feode Mcp, apply this rule, and every submit_machining_rfq call is checked against it from then on.
Questions about submit_machining_rfq
Submit a structured machining/testing RFQ. Runs a lightweight compliance screen (prohibited-use + sanctions) and, if cleared, registers the enquiry for human follow-up from enquiry@feode.com. Not a contract or quotation; no payment is taken here. You must provide the legal entity behind the request. It is categorised as a Write tool in the Feode Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
submit_machining_rfq accepts 12 parameters: email, notes, company, country, end_use, industry, material, quantity, tolerance, drawing_url, contact_name, part_description. Required: email, company, country, end_use, material, quantity, contact_name, part_description. The full parameter table on this page comes from the server's own tool schema.
Register the Feode MCP server in PolicyLayer and add a rule for submit_machining_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 Feode Mcp. Nothing to install.
submit_machining_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 submit_machining_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 submit_machining_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.
submit_machining_rfq is provided by the Feode MCP server (https://www.feode.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Feode, and thousands of servers like it.
This server
Across the catalogue