geomech_effective_stress

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/geomech-effective-stress.md

WHAT IT DOES

What geomech_effective_stress does on pyResToolbox MCP Server

AI agents call geomech_effective_stress 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 geomech_effective_stress is rated Low

Based on the server context (petroleum engineering calculations) and the tool name implying a stress calculation, this is most likely a read/compute operation that returns a calculated value with no side effects. However, the empty description lowers confidence significantly. Effective stress calculations are standard reservoir geomechanics computations with no destructive or financial implications.

From the tool's definition Tool name 'geomech_effective_stress' suggests a geomechanics calculation (effective stress computation), consistent with the server's petroleum engineering calculations theme. Description is empty.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs geomech_effective_stress 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 geomech_effective_stress, this is the rule to start with:

geomech_effective_stress Allowed

geomech_effective_stress 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": {
    "geomech_effective_stress": {}
  }
}

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 geomech_effective_stress call is checked against it from then on.

FAQ

Questions about geomech_effective_stress

What does the geomech_effective_stress tool do? +

geomech_effective_stress 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 geomech_effective_stress? +

Register the pyResToolbox MCP Server MCP server in PolicyLayer and add a rule for geomech_effective_stress: 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 geomech_effective_stress? +

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

Can I rate-limit geomech_effective_stress? +

Yes. Add a rate_limit block to the geomech_effective_stress 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 geomech_effective_stress completely? +

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

geomech_effective_stress 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 →