fieldpulse · Pulsenetwork MCP: Risk & Policy

WHAT IT DOES

What fieldpulse does on Pulsenetwork

AI agents call fieldpulse to retrieve information from Pulsenetwork without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

PARAMETERS

Parameter	Type	Required	Description
`lat`	string	—	Latitude (alternative to region name). Required unless region is given.
`lon`	string	—	Longitude (alternative to region name). Required unless region is given.
`crop`	string	—	Crop: wheat, corn, rice, soybeans, cotton, coffee, cocoa, palm-oil, canola, barley, sorghum
`lang`	string	—	Response language ISO 639-1
`action`	string	Yes	Which endpoint to call. Options: yield-forecast \| weather-risk \| soil-intel \| pest-disease \| irrigation \| commodity-outlook \| input-cost \| planting-window \| sea
`region`	string	—	Named region: 'Black Sea', 'US Midwest', 'Brazil Mato Grosso', 'India Punjab', 'EU', 'Australia', 'Global'. Required unless lat+lon are both given.
`hectares`	string	—	Farm size in hectares (optional — enables total cost estimate)
`soil_type`	string	—	Soil type: sandy, loam, clay, silt-loam, sandy-loam, clay-loam

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why fieldpulse needs a policy

FieldPulse is a querying/analytics tool that aggregates public and commercial agricultural data into structured reports. Users pay per query via x402 protocol, but the tool itself only retrieves and synthesizes information—it has no side effects on external systems, does not modify user data, and does not execute arbitrary operations. The financial transaction (USDC payment) is a billing mechanism, not a tool action.

From the tool's definition All endpoints are data retrieval operations: 'yield-forecast', 'weather-risk', 'soil-intel', 'pest-disease', and 'irrigation' synthesize and return intelligence from existing data sources (satellite NDVI, weather APIs, USDA, FAO, EPPO).

Attacks that exploit this kind of access

Questions about fieldpulse

What does the fieldpulse tool do? +

FieldPulse: Global precision agriculture intelligence API. Synthesizes satellite NDVI data, Open-Meteo soil/weather data, USDA WASDE, FAO, and EPPO into structured, actionable intelligence for growers, agronomist Coverage: Global Endpoints: • yield-forecast ($0.15): Yield and production forecast for any crop and region • weather-risk ($0.08): 7-14 day crop-specific weather risk assessment • soil-intel ($0.08): Live soil moisture, temperature, and evapotranspiration intelligence • pest-disease ($0.10): Pest and disease risk assessment with outbreak alerts • irrigation ($0.08): ET0-based irrigation recommendation and water budget • commodity-outlook ($0.10): Agricultural commodity market outlook and price intelligence • input-cost ($0.08): Fertilizer, seed, and crop protection cost intelligence • planting-window ($0.05): Optimal planting window based on soil temperature and frost dates • season-brief ($0.20): Comprehensive seasonal agricultural intelligence brief • crop-health ($0.10): Crop health assessment from satellite + soil data. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.

What parameters does fieldpulse accept? +

fieldpulse accepts 8 parameters: lat, lon, crop, lang, action, region, hectares, soil_type. Required: action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fieldpulse? +

Register the Pulsenetwork MCP server in PolicyLayer and add a rule for fieldpulse: 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 Pulsenetwork. Nothing to install.

What risk level is fieldpulse? +

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

Can I rate-limit fieldpulse? +

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

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

fieldpulse is provided by the Pulsenetwork MCP server (https://pulse.theaslangroupllc.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.