get_parameter_definitions

Get information about valid parameter values for NOAA API requests

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

What get_parameter_definitions does on LocalTides MCP Server

AI agents call get_parameter_definitions 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_parameter_definitions needs a policy

This tool retrieves reference information about valid parameter values for API requests. It is a pure read operation with no side effects, data modification, code execution, or destructive capability. The information returned is static reference material. Severity is low because misuse poses minimal risk—an agent could only retrieve publicly available API documentation.

From the tool's definition Tool name 'get_parameter_definitions' and description 'Get information about valid parameter values for NOAA API requests' indicate a retrieval operation with no modification or execution of external code. The tool queries metadata about API parameters.

Questions about get_parameter_definitions

What does the get_parameter_definitions tool do? +

Get information about valid parameter values for NOAA API requests. 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_parameter_definitions? +

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

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

Can I rate-limit get_parameter_definitions? +

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

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

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