biopulse

SERVERPulsenetwork SOURCEhttps://pulse.theaslangroupllc.com/api/mcp

Low RISK CLASS

Category Read

Parameters 111 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-theaslangroupllc-pulse-pulsenetwork/biopulse.md

WHAT IT DOES

What biopulse does on Pulsenetwork

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

Parameter	Type	Required	Description
`lat`	string	—	lat
`lng`	string	—	lng
`dist`	string	—	Search radius in km (max 50, default 25)
`lang`	string	—	lang
`group`	string	—	bird \| mammal \| reptile \| amphibian \| insect \| plant \| other
`action`	string	Yes	Which endpoint to call. Options: species \| sightings \| birding \| invasive \| endangered \| hotspot \| identify \| migrate \| marine
`radius`	string	—	Radius in km (max 100, default 25)
`region`	string	—	Country, state, province, or region name
`species`	string	—	Common or scientific name
`location`	string	—	location
`description`	string	—	What you observed — size, color, behavior, habitat

Parameters from the server's own tool schema.

RISK

Why biopulse is rated Low

BioPulse is a biodiversity data synthesis and retrieval API that aggregates information from GBIF, IUCN, eBird, and iNaturalist. All documented endpoints are informational queries that retrieve existing data without modification, deletion, or execution of code. The tool poses minimal risk even if misused by an agent, as it can only surface publicly available biodiversity intelligence.

From the tool's definition Tool description states 'Species profiles, IUCN conservation status, sighting reports, birding hotspots, migration tracking, endangered s[pecies]' and all endpoints (species, sightings, birding, invasive, endangered, hotspot, identify, migrate) perform data…

Risk signalsHigh parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs biopulse safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pulsenetwork, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For biopulse, this is the rule to start with:

biopulse Allowed

biopulse is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "biopulse": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pulsenetwork, apply this rule, and every biopulse call is checked against it from then on.

FAQ

Questions about biopulse

What does the biopulse tool do? +

BioPulse: Global biodiversity intelligence API. GBIF + IUCN + eBird + iNaturalist data synthesis. Species profiles, IUCN conservation status, sighting reports, birding hotspots, migration tracking, endangered s Coverage: Global Endpoints: • species ($0.12): Species profile • sightings ($0.08): Recent wildlife sightings • birding ($0.10): Birding intelligence • invasive ($0.08): Invasive species alerts • endangered ($0.10): Endangered species profile • hotspot ($0.10): Biodiversity hotspot guide • identify ($0.12): Species identification • migrate ($0.10): Migration intelligence • marine ($0.10): Marine biodiversity. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.

What parameters does biopulse accept? +

biopulse accepts 11 parameters: lat, lng, dist, lang, group, action, radius, region, species, location, description. Required: action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on biopulse? +

Register the Pulsenetwork MCP server in PolicyLayer and add a rule for biopulse: 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 biopulse? +

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

Can I rate-limit biopulse? +

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

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

biopulse 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.

KEEP EXPLORING

More on Pulsenetwork, and thousands of servers like it.

This server

All 80 Pulsenetwork tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →