get_sea_level_trends

Get sea level trends and error margins for a station

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

What get_sea_level_trends does on LocalTides MCP Server

AI agents call get_sea_level_trends 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_sea_level_trends needs a policy

This tool retrieves historical sea level trend data from NOAA for analysis purposes. It performs no modifications, deletions, or external operations—it simply queries and returns publicly available scientific data. The blast radius of misuse is minimal; an agent cannot cause harm by repeatedly calling this endpoint or requesting data for different stations. This is a straightforward Read operation.

From the tool's definition Tool name 'get_sea_level_trends' and description 'Get sea level trends and error margins for a station' indicate data retrieval with no side effects. The verb 'Get' and the nature of returning 'trends and error margins' confirm this is a query operation.

Questions about get_sea_level_trends

What does the get_sea_level_trends tool do? +

Get sea level trends and error margins 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_sea_level_trends? +

Register the LocalTides MCP Server MCP server in PolicyLayer and add a rule for get_sea_level_trends: 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_sea_level_trends? +

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

Can I rate-limit get_sea_level_trends? +

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

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

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