get_high_tide_flooding_likelihoods

Get high tide flooding daily likelihoods for a station

Server LocalTides MCP Server ryancardin15/noaa-tidesandcurrents-mcp
Category Read
Risk class Low
Parameters 00 required

What get_high_tide_flooding_likelihoods does on LocalTides MCP Server

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

Why get_high_tide_flooding_likelihoods needs a policy

This tool retrieves high tide flooding probability data from NOAA for a specified station. It performs no modifications, deletions, or external operations—purely a read operation querying existing data. The low severity reflects minimal blast radius: inaccurate results could inform poor water safety decisions, but cannot directly cause harm.

From the tool's definition Tool name 'get_high_tide_flooding_likelihoods' and description 'Get high tide flooding daily likelihoods for a station' indicate a data retrieval operation.

Questions about get_high_tide_flooding_likelihoods

What does the get_high_tide_flooding_likelihoods tool do? +

Get high tide flooding daily likelihoods for a station. It is categorised as a Read tool in the LocalTides MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_high_tide_flooding_likelihoods? +

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

What risk level is get_high_tide_flooding_likelihoods? +

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

Can I rate-limit get_high_tide_flooding_likelihoods? +

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

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

get_high_tide_flooding_likelihoods is provided by the LocalTides MCP Server MCP server (ryancardin15/noaa-tidesandcurrents-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.