read_raster
AI agents call read_raster to retrieve information from LocuSync Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name strongly suggests data retrieval rather than modification or execution. Raster data reading is a standard GIS operation that queries spatial datasets without side effects. The empty description reduces confidence slightly, but the semantic meaning of 'read_' combined with the server's declared purpose (process GIS file formats, perform spatial analysis) indicates a Read operation.
From the tool's definition Tool name 'read_raster' indicates reading/retrieving raster geospatial data; prefix 'read' and the context of a geospatial server support retrieval operations. Tool description is empty, limiting direct evidence.
Attacks that exploit this kind of access
read_raster. It is categorised as a Read tool in the LocuSync Server MCP Server, which means it retrieves data without modifying state.
Register the LocuSync Server MCP server in PolicyLayer and add a rule for read_raster: 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 LocuSync Server. Nothing to install.
read_raster 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 read_raster 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 read_raster. 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.
read_raster is provided by the LocuSync Server MCP server (matbel91765/gis-mcp-server). 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 →