flowing_bhp
A execute tool on the pyResToolbox MCP server.
This record as markdown: /tools/gabrielserrao-pyrestoolbox-mcp/flowing-bhp.md
What flowing_bhp does on pyResToolbox MCP Server
AI agents invoke flowing_bhp 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 flowing_bhp is rated High
The description is empty, so classification relies on the tool name alone. 'flowing_bhp' most likely computes flowing bottomhole pressure, a read/calculate operation. Given the server context of petroleum engineering calculations, this is likely a computational/execute-type operation (running a model), but with no description, confidence is low.
From the tool's definition Tool name 'flowing_bhp' and server description mentions 'well performance modeling' — flowing bottomhole pressure is a standard petroleum engineering calculation.
Attacks that exploit this kind of access
The rule that runs flowing_bhp 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 flowing_bhp, this is the rule to start with:
flowing_bhp 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 flowing_bhp call is checked against it from then on.
Questions about flowing_bhp
flowing_bhp 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 flowing_bhp: 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.
flowing_bhp 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 flowing_bhp 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 flowing_bhp. 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.
flowing_bhp 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