fit_relative_permeability
A execute tool on the pyResToolbox MCP server.
This record as markdown: /tools/gabrielserrao-pyrestoolbox-mcp/fit-relative-permeability.md
What fit_relative_permeability does on pyResToolbox MCP Server
AI agents invoke fit_relative_permeability to trigger actions in pyResToolbox MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why fit_relative_permeability is rated High
With an empty description, I cannot determine the exact behavior. Based on the name, this tool likely fits (computes/models) relative permeability curves — a calculation operation typical in reservoir simulation support. This is most consistent with Execute (runs a computation/model fitting). Confidence is low due to the empty description.
From the tool's definition Tool name 'fit_relative_permeability' and empty description. Server context involves petroleum engineering calculations including PVT analysis and reservoir simulation support.
Attacks that exploit this kind of access
The rule that runs fit_relative_permeability 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 fit_relative_permeability, this is the rule to start with:
fit_relative_permeability stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 fit_relative_permeability call is checked against it from then on.
Questions about fit_relative_permeability
fit_relative_permeability is a execute tool on the pyResToolbox MCP Server MCP server. It is categorised as a Execute tool in the pyResToolbox MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the pyResToolbox MCP Server MCP server in PolicyLayer and add a rule for fit_relative_permeability: 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.
fit_relative_permeability is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the fit_relative_permeability 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 fit_relative_permeability. 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.
fit_relative_permeability 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.
Across the catalogue