estimated_ultimate_recovery

A read tool on the pyResToolbox MCP server.

SERVERpyResToolbox MCP Server SOURCEgabrielserrao/pyrestoolbox-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gabrielserrao-pyrestoolbox-mcp/estimated-ultimate-recovery.md

WHAT IT DOES

What estimated_ultimate_recovery does on pyResToolbox MCP Server

AI agents call estimated_ultimate_recovery to retrieve information from pyResToolbox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why estimated_ultimate_recovery is rated Low

Based on the tool name, 'estimated_ultimate_recovery' (EUR) is a standard petroleum engineering calculation that estimates the total recoverable hydrocarbons from a well or reservoir. This is a read/calculation operation with no side effects.

From the tool's definition Tool name 'estimated_ultimate_recovery'; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs estimated_ultimate_recovery safely

PolicyLayer is an MCP gateway: it sits between your AI agents and pyResToolbox MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For estimated_ultimate_recovery, this is the rule to start with:

estimated_ultimate_recovery Allowed

estimated_ultimate_recovery is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "estimated_ultimate_recovery": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect pyResToolbox MCP Server, apply this rule, and every estimated_ultimate_recovery call is checked against it from then on.

FAQ

Questions about estimated_ultimate_recovery

What does the estimated_ultimate_recovery tool do? +

estimated_ultimate_recovery is a read tool on the pyResToolbox MCP Server MCP server. It is categorised as a Read tool in the pyResToolbox MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on estimated_ultimate_recovery? +

Register the pyResToolbox MCP Server MCP server in PolicyLayer and add a rule for estimated_ultimate_recovery: 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 pyResToolbox MCP Server. Nothing to install.

What risk level is estimated_ultimate_recovery? +

estimated_ultimate_recovery is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit estimated_ultimate_recovery? +

Yes. Add a rate_limit block to the estimated_ultimate_recovery 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.

How do I block estimated_ultimate_recovery completely? +

Set action: deny in the PolicyLayer policy for estimated_ultimate_recovery. 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.

What MCP server provides estimated_ultimate_recovery? +

estimated_ultimate_recovery is provided by the pyResToolbox MCP Server MCP server (gabrielserrao/pyrestoolbox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on pyResToolbox MCP Server, and thousands of servers like it.

This server

All 108 pyResToolbox MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →