Get ocean/wave forecast for a coastal city (CPTEC/INPE)
AI agents call get_cptec_ocean_forecast to retrieve information from Mcp Ap2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries weather/ocean data from an external source (CPTEC/INPE) and returns it to the user. It is a pure read operation with no side effects. The tool performs no financial transactions, does not execute arbitrary code, and does not modify any system state. Despite being hosted on a payment protocol server (AP2), this particular tool is a simple data retrieval function with minimal security risk.
From the tool's definition Tool name and description: 'Get ocean/wave forecast for a coastal city' — retrieves forecast data with no modification, creation, or deletion of data. Returns information only.
Documented attack patterns abuse exactly the kind of access get_cptec_ocean_forecast gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for get_cptec_ocean_forecast:
{
"version": "1",
"default": "deny",
"tools": {
"get_cptec_ocean_forecast": {}
}
} get_cptec_ocean_forecast is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get ocean/wave forecast for a coastal city (CPTEC/INPE). It is categorised as a Read tool in the Mcp Ap2 MCP Server, which means it retrieves data without modifying state.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for get_cptec_ocean_forecast: 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 Mcp Ap2. Nothing to install.
get_cptec_ocean_forecast 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_cptec_ocean_forecast 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_cptec_ocean_forecast. 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_cptec_ocean_forecast is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.