search_capabilities
Keyword search across FEODE products/specs. e.g. 'subsea wellhead 15000 psi', 'one trip abandonment', 'continuous circulation'.
This record as markdown: /tools/com-feode-feode-mcp/search-capabilities.md
What search_capabilities does on Feode Mcp
AI agents call search_capabilities 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 |
|---|---|---|---|
query | string | Yes |
Parameters from the server's own tool schema.
Why search_capabilities is rated Low
This tool performs information retrieval only. It searches and returns product specifications and capabilities without creating, modifying, executing, deleting, or committing financial resources. The examples ('subsea wellhead 15000 psi', 'one trip abandonment', 'continuous circulation') are search queries, not directives that trigger external actions or state changes.
From the tool's definition Tool name 'search_capabilities' and description indicates 'Keyword search across FEODE products/specs' — a query-based retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs search_capabilities 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 search_capabilities, this is the rule to start with:
search_capabilities 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 search_capabilities call is checked against it from then on.
Questions about search_capabilities
Keyword search across FEODE products/specs. e.g. 'subsea wellhead 15000 psi', 'one trip abandonment', 'continuous circulation'. It is categorised as a Read tool in the Feode Mcp MCP Server, which means it retrieves data without modifying state.
search_capabilities accepts 1 parameter: query. Required: query. 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 search_capabilities: 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.
search_capabilities 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 search_capabilities 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 search_capabilities. 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.
search_capabilities 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