geomech_rock_strength_mohr_coulomb
A other tool on the pyResToolbox MCP server.
This record as markdown: /tools/gabrielserrao-pyrestoolbox-mcp/geomech-rock-strength-mohr-coulomb.md
What geomech_rock_strength_mohr_coulomb does on pyResToolbox MCP Server
AI agents call geomech_rock_strength_mohr_coulomb as a supporting operation in pyResToolbox MCP Server workflows.
Why geomech_rock_strength_mohr_coulomb is rated Low
The tool name suggests it performs petroleum geomechanics calculations (rock strength via Mohr-Coulomb criterion), which would be a read/compute operation returning engineering values. The description is empty, lowering confidence. Given the server context of petroleum engineering calculations, this is most likely a pure numerical calculation with no side effects, fitting the Read category.
From the tool's definition Tool name 'geomech_rock_strength_mohr_coulomb' and empty description. Based on naming, likely performs geomechanical rock strength calculations using Mohr-Coulomb failure criterion.
Attacks that exploit this kind of access
The rule that runs geomech_rock_strength_mohr_coulomb 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_rock_strength_mohr_coulomb, this is the rule to start with:
geomech_rock_strength_mohr_coulomb gets a rate cap, and everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect pyResToolbox MCP Server, apply this rule, and every geomech_rock_strength_mohr_coulomb call is checked against it from then on.
Questions about geomech_rock_strength_mohr_coulomb
geomech_rock_strength_mohr_coulomb is a other tool on the pyResToolbox MCP Server MCP server. It is categorised as a Other tool in the pyResToolbox MCP Server MCP Server, which means it performs auxiliary operations.
Register the pyResToolbox MCP Server MCP server in PolicyLayer and add a rule for geomech_rock_strength_mohr_coulomb: 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.
geomech_rock_strength_mohr_coulomb is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the geomech_rock_strength_mohr_coulomb 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 geomech_rock_strength_mohr_coulomb. 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.
geomech_rock_strength_mohr_coulomb 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.
More on pyResToolbox MCP Server, and thousands of servers like it.
This server
Across the catalogue