Get currents data for a station
AI agents call get_currents 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.
This tool retrieves currents data from the NOAA Tides and Currents API for a specified station. It performs a simple data query with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an agent could only retrieve historical or current currents information, which is public oceanographic data. This is a straightforward read operation with low security risk.
From the tool's definition Tool name 'get_currents' with description 'Get currents data for a station' indicates a retrieval operation.
Attacks that exploit this kind of access
Get currents data 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.
Register the LocalTides MCP Server MCP server in PolicyLayer and add a rule for get_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 LocalTides MCP Server. Nothing to install.
get_currents is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_currents 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.
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 →