geomech_shear_failure_criteria
A other tool on the pyResToolbox MCP server.
This record as markdown: /tools/gabrielserrao-pyrestoolbox-mcp/geomech-shear-failure-criteria.md
What geomech_shear_failure_criteria does on pyResToolbox MCP Server
AI agents call geomech_shear_failure_criteria as a supporting operation in pyResToolbox MCP Server workflows.
Why geomech_shear_failure_criteria is rated Low
The tool name suggests it performs geomechanical calculations related to shear failure criteria (e.g., Mohr-Coulomb or similar). Based on the server context (petroleum engineering calculations) and sibling tools (all computational/analytical), this is almost certainly a read/calculation tool returning computed values with no side effects. However, the description is empty, lowering confidence.
From the tool's definition Tool name 'geomech_shear_failure_criteria' and empty description; name suggests geomechanical shear failure criteria calculation, likely a read/compute operation
Attacks that exploit this kind of access
The rule that runs geomech_shear_failure_criteria 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_shear_failure_criteria, this is the rule to start with:
geomech_shear_failure_criteria 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_shear_failure_criteria call is checked against it from then on.
Questions about geomech_shear_failure_criteria
geomech_shear_failure_criteria 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_shear_failure_criteria: 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_shear_failure_criteria 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_shear_failure_criteria 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_shear_failure_criteria. 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_shear_failure_criteria 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