ok_wells_search

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 50 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/ok-wells-search.md

WHAT IT DOES

What ok_wells_search does on Livedatalink

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

Parameter	Type	Required	Description
`api`	string	—	API well number (digits; non-digits are ignored).
`limit`	number	—	Max well records to return (default 25, max 100). The total matching count is always reported.
`county`	string	—	Oklahoma county name (e.g. 'Canadian', 'Kingfisher', 'Grady'). Matched case-insensitively.
`operator`	string	—	Operator name or fragment (e.g. 'Chesapeake', 'Devon'). Substring, case-insensitive.
`well_type`	string	—	Filter by well type: OIL, GAS, DRY, SWD (saltwater disposal), etc.

Parameters from the server's own tool schema.

RISK

Why ok_wells_search is rated Low

Even though ok_wells_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs ok_wells_search safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For ok_wells_search, this is the rule to start with:

ok_wells_search Allowed

ok_wells_search 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": {
    "ok_wells_search": {}
  }
}

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

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

FAQ

Questions about ok_wells_search

What does the ok_wells_search tool do? +

Search Oklahoma oil & gas wells by county, operator, API number, and/or well type using the Oklahoma Corporation Commission (OCC) RBDMS well database (keyless public record). Unlike a pure map layer, this returns the OPERATOR, well status, well type (OIL/GAS/DRY/etc.), well name, county, and location for each match, plus the total matching count and a by-operator/by-type breakdown. Use it for 'who operates wells in county X', 'how many wells does operator Y have', or an operator's well portfolio. Oklahoma covers the Anadarko Basin / SCOOP / STACK plays. At least one of county, operator, or api is recommended to narrow the search. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does ok_wells_search accept? +

ok_wells_search accepts 5 parameters: api, limit, county, operator, well_type. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on ok_wells_search? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for ok_wells_search: 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 Livedatalink. Nothing to install.

What risk level is ok_wells_search? +

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

Can I rate-limit ok_wells_search? +

Yes. Add a rate_limit block to the ok_wells_search 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 ok_wells_search completely? +

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

ok_wells_search is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 280 Livedatalink tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

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