list_items_temporal
AI agents call list_items_temporal to retrieve information from OpenLandMap MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to list or retrieve catalog items filtered by temporal criteria. It performs no modifications, deletions, or financial operations. The naming pattern and server purpose (discovery and retrieval of environmental datasets) indicate a read-only data query operation with minimal blast radius. Lower confidence due to empty description, but functional context strongly suggests Read category.
From the tool's definition Tool name 'list_items_temporal' suggests querying/listing data by temporal parameters. Server context indicates data discovery and retrieval from a STAC catalog of geospatial datasets.
Attacks that exploit this kind of access
list_items_temporal. It is categorised as a Read tool in the OpenLandMap MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenLandMap MCP Server MCP server in PolicyLayer and add a rule for list_items_temporal: 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 OpenLandMap MCP Server. Nothing to install.
list_items_temporal 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 list_items_temporal 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 list_items_temporal. 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.
list_items_temporal is provided by the OpenLandMap MCP Server MCP server (tharlestsa/openlandmap_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 →