Return the GeoJSON boundary polygon for a PLSS or Texas TXSS legal land description.
AI agents call plss_to_geojson to retrieve information from Townshipamerica without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and formats existing geographic boundary data from PLSS/TXSS legal descriptions into GeoJSON format. It performs a read-only lookup and data transformation with no side effects, no data modification, no code execution, and no destructive or financial implications. The operation is purely informational.
From the tool's definition Tool description states 'Return the GeoJSON boundary polygon' — a retrieval operation that queries and returns geographic boundary data without modifying, deleting, or executing arbitrary operations.
Attacks that exploit this kind of access
Return the GeoJSON boundary polygon for a PLSS or Texas TXSS legal land description. It is categorised as a Read tool in the Townshipamerica MCP Server, which means it retrieves data without modifying state.
Register the Townshipamerica MCP server in PolicyLayer and add a rule for plss_to_geojson: 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 Townshipamerica. Nothing to install.
plss_to_geojson 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 plss_to_geojson 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 plss_to_geojson. 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.
plss_to_geojson is provided by the Townshipamerica MCP server (townshipamerica/python-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 →