get_drill_pipe_specs
Full NOV Grant Prideco performance specs for one drill string item by id: pipe-body new/premium torsional & tensile yield, internal pressure, collapse; tool-joint OD/ID, make-up torque max/min, drift, torsional yield. Use list_drill_pipe for ids.
This record as markdown: /tools/com-feode-feode-mcp/get-drill-pipe-specs.md
What get_drill_pipe_specs does on Feode Mcp
AI agents call get_drill_pipe_specs to retrieve information from Feode Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Item id, e.g. dp-5-19.50-s135-nc50 |
Parameters from the server's own tool schema.
Why get_drill_pipe_specs is rated Low
This tool retrieves technical specifications (torsional yield, tensile yield, internal pressure, collapse ratings, etc.) for drill pipe equipment. It performs a read-only query by item ID and returns static specification data. There is no modification, deletion, execution of arbitrary commands, or financial impact. The tool is purely informational retrieval, making it a low-severity Read operation.
From the tool's definition Tool name 'get_drill_pipe_specs' and description indicate retrieval of performance specifications by ID. Language like 'Full NOV Grant Prideco performance specs for one drill string item' and 'Use list_drill_pipe for ids' confirms a lookup/query operation…
Attacks that exploit this kind of access
The rule that runs get_drill_pipe_specs 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 get_drill_pipe_specs, this is the rule to start with:
get_drill_pipe_specs is read-only, so it stays allowed. 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 get_drill_pipe_specs call is checked against it from then on.
Questions about get_drill_pipe_specs
Full NOV Grant Prideco performance specs for one drill string item by id: pipe-body new/premium torsional & tensile yield, internal pressure, collapse; tool-joint OD/ID, make-up torque max/min, drift, torsional yield. Use list_drill_pipe for ids. It is categorised as a Read tool in the Feode Mcp MCP Server, which means it retrieves data without modifying state.
get_drill_pipe_specs accepts 1 parameter: id. Required: id. 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 get_drill_pipe_specs: 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.
get_drill_pipe_specs is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_drill_pipe_specs 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 get_drill_pipe_specs. 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.
get_drill_pipe_specs 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