# 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.

Agent View of the PolicyLayer registry record for `submit_machining_rfq`. HTML page: https://policylayer.com/tools/com-feode-feode-mcp/submit-machining-rfq

## Facts

- Tool: `submit_machining_rfq`
- Server: Feode Mcp (`https://www.feode.com/mcp`) — https://policylayer.com/tools/com-feode-feode-mcp.md
- Homepage: https://github.com/FarEastAI/feode-mcp
- Risk category: Write (Medium risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 12 (8 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `email` | string | yes | Contact email |
| `notes` | string | no | 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 | no | Industry sector |
| `material` | string | yes | Material / grade |
| `quantity` | string | yes | Quantity |
| `tolerance` | string | no | Key tolerances (optional) |
| `drawing_url` | string | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "submit_machining_rfq",
    "arguments": {
      "email": "<email>",
      "company": "<company>",
      "country": "<country>",
      "end_use": "<end_use>",
      "material": "<material>",
      "quantity": "<quantity>",
      "contact_name": "<contact_name>",
      "part_description": "<part_description>"
    }
  }
}
```

## 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 own 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 signals: High parameter count (12 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Feode Mcp:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_machining_rfq": {
      "limits": [
        {
          "counter": "submit_machining_rfq_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Feode Mcp (11)

- `get_certifications` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-certifications.md
- `get_company_profile` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-company-profile.md
- `get_drill_pipe_specs` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-drill-pipe-specs.md
- `get_drill_string_guidance` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-drill-string-guidance.md
- `get_machining_services` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-machining-services.md
- `get_machining_terms` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-machining-terms.md
- `get_product_specs` — Read — https://policylayer.com/tools/com-feode-feode-mcp/get-product-specs.md
- `list_drill_pipe` — Read — https://policylayer.com/tools/com-feode-feode-mcp/list-drill-pipe.md
- `list_products` — Read — https://policylayer.com/tools/com-feode-feode-mcp/list-products.md
- `search_capabilities` — Read — https://policylayer.com/tools/com-feode-feode-mcp/search-capabilities.md
- `search_drill_pipe` — Read — https://policylayer.com/tools/com-feode-feode-mcp/search-drill-pipe.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-feode-feode-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-feode-feode-mcp