noaa-tides-currents

Get current speed/direction observations from a NOAA CO-OPS station.

SERVERMeta Data Mcp SOURCEpypi:meta-data-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/io-github-derekslinz-meta-data-mcp/noaa-tides-currents.md

WHAT IT DOES

What noaa-tides-currents does on Meta Data Mcp

AI agents call noaa-tides-currents to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why noaa-tides-currents is rated Low

This tool queries public NOAA oceanographic observations and returns environmental data. It performs a pure read operation against a government data API with no side effects, no code execution, and no data modification. The blast radius of misuse is minimal—an agent could only retrieve publicly available tidal and current data, which poses no security or operational risk.

From the tool's definition Tool name 'noaa-tides-currents' and description 'Get current speed/direction observations from a NOAA CO-OPS station' indicate a retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs noaa-tides-currents safely

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

noaa-tides-currents Allowed

noaa-tides-currents 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": {
    "noaa-tides-currents": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Meta Data Mcp, apply this rule, and every noaa-tides-currents call is checked against it from then on.

FAQ

Questions about noaa-tides-currents

What does the noaa-tides-currents tool do? +

Get current speed/direction observations from a NOAA CO-OPS station. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on noaa-tides-currents? +

Register the Meta Data MCP server in PolicyLayer and add a rule for noaa-tides-currents: 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 Meta Data Mcp. Nothing to install.

What risk level is noaa-tides-currents? +

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

Can I rate-limit noaa-tides-currents? +

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

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

noaa-tides-currents is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meta Data, and thousands of servers like it.

This server

All 396 Meta Data tools →

Across the catalogue

The MCP Attack Database →

Guides

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