oil_viscosity

A read tool on the pyResToolbox MCP server.

SERVERpyResToolbox MCP Server SOURCEgabrielserrao/pyrestoolbox-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/gabrielserrao-pyrestoolbox-mcp/oil-viscosity.md

WHAT IT DOES

What oil_viscosity does on pyResToolbox MCP Server

AI agents call oil_viscosity to retrieve information from pyResToolbox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why oil_viscosity is rated Low

Based on the tool name and server context (petroleum engineering calculations, PVT analysis), this tool likely computes or retrieves oil viscosity values using correlations — a read/calculation operation with no side effects. Confidence is reduced due to the empty description.

From the tool's definition Tool name is 'oil_viscosity'; description is empty and uninformative.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs oil_viscosity 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 oil_viscosity, this is the rule to start with:

oil_viscosity Allowed

oil_viscosity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "oil_viscosity": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect pyResToolbox MCP Server, apply this rule, and every oil_viscosity call is checked against it from then on.

FAQ

Questions about oil_viscosity

What does the oil_viscosity tool do? +

oil_viscosity is a read tool on the pyResToolbox MCP Server MCP server. It is categorised as a Read tool in the pyResToolbox MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on oil_viscosity? +

Register the pyResToolbox MCP Server MCP server in PolicyLayer and add a rule for oil_viscosity: 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.

What risk level is oil_viscosity? +

oil_viscosity is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit oil_viscosity? +

Yes. Add a rate_limit block to the oil_viscosity 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.

How do I block oil_viscosity completely? +

Set action: deny in the PolicyLayer policy for oil_viscosity. 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.

What MCP server provides oil_viscosity? +

oil_viscosity 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.

KEEP EXPLORING

More on pyResToolbox MCP Server, and thousands of servers like it.

This server

All 108 pyResToolbox MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →