generate_rel_perm_table
A write tool on the pyResToolbox MCP server.
This record as markdown: /tools/gabrielserrao-pyrestoolbox-mcp/generate-rel-perm-table.md
What generate_rel_perm_table does on pyResToolbox MCP Server
AI agents use generate_rel_perm_table to create or update resources in pyResToolbox MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your pyResToolbox MCP Server environment.
Why generate_rel_perm_table is rated Medium
The 'generate' verb combined with 'table' creation suggests data generation/creation rather than simple retrieval. This fits the Write category (creates or modifies data reversibly). Severity is medium because generated simulation tables are intermediate outputs used for engineering analysis; misuse could lead to incorrect reservoir models, but the data is recalculated and not destructive.
From the tool's definition Tool name 'generate_rel_perm_table' indicates creation of a relative permeability table. No description provided, but context shows this is a petroleum engineering calculation tool within a reservoir simulation support suite.
Attacks that exploit this kind of access
The rule that runs generate_rel_perm_table 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 generate_rel_perm_table, this is the rule to start with:
generate_rel_perm_table stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 generate_rel_perm_table call is checked against it from then on.
Questions about generate_rel_perm_table
generate_rel_perm_table is a write tool on the pyResToolbox MCP Server MCP server. It is categorised as a Write tool in the pyResToolbox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the pyResToolbox MCP Server MCP server in PolicyLayer and add a rule for generate_rel_perm_table: 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.
generate_rel_perm_table is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the generate_rel_perm_table 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 generate_rel_perm_table. 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.
generate_rel_perm_table 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