calculate_vshale
AI agents call calculate_vshale to retrieve information from Petropt/petro without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
V-shale (volume of shale) calculation is a standard read/compute operation in petrophysics that derives a value from input log data. Sibling tools like calculate_density_porosity, calculate_net_pay, and calculate_archie_sw follow the same read/calculate pattern. The empty description lowers confidence, but the naming convention strongly implies a pure calculation with no destructive, financial, or write side effects.
From the tool's definition Tool name 'calculate_vshale' on a petroleum engineering server; description is empty. 'calculate_vshale' refers to calculating volume of shale from well log data, a standard petrophysical computation with no side effects.
Attacks that exploit this kind of access
calculate_vshale. It is categorised as a Read tool in the Petropt/petro MCP Server, which means it retrieves data without modifying state.
Register the Petropt/petro MCP server in PolicyLayer and add a rule for calculate_vshale: 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 Petropt/petro. Nothing to install.
calculate_vshale is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the calculate_vshale 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 calculate_vshale. 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.
calculate_vshale is provided by the Petropt/petro MCP server (petropt/petro-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →