herbapulse · Pulsenetwork MCP: Risk & Policy

WHAT IT DOES

What herbapulse does on Pulsenetwork

AI agents call herbapulse 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
`drug`	string	—	drug
`herb`	string	—	herb
`lang`	string	—	lang
`type`	string	—	naturopath \| herbalist \| tcm \| ayurveda \| homeopath \| integrative-md
`topic`	string	—	anxiety \| pain \| sleep \| epilepsy \| nausea \| inflammation \| general
`action`	string	Yes	Which endpoint to call. Options: herb \| remedy \| ingredient \| interaction \| skin \| tradition \| practitioner \| cannabis
`concern`	string	—	anti-aging \| acne \| hydration \| sensitivity
`product`	string	—	product
`compound`	string	—	Default: both
`location`	string	—	location
`condition`	string	—	condition
`tradition`	string	—	tradition

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why herbapulse needs a policy

HerbaPulse is a pure information retrieval service offering lookups and reference data about herbal medicine, botanical information, and drug-herb interactions. Even the interaction checker is a read operation that returns advisory information rather than executing medical actions or making changes. The financial aspect (pay-per-query) is infrastructure, not a capability of the tool itself.

From the tool's definition All endpoints are queries: 'Herb profile', 'Cross-cultural remedy lookup', 'Supplement decoder', 'Herb-drug interaction checker', 'Natural skincare ingredient', 'Healing tradition deep dive', 'Practitioner guide'.

Risk signalsHigh parameter count (14 properties)

Attacks that exploit this kind of access

Questions about herbapulse

What does the herbapulse tool do? +

HerbaPulse: Global herbal medicine and botanical intelligence API. PubMed-grounded herb profiles, drug-herb interaction checker, traditional medicine system guides (Ayurveda, TCM, Amazonian, African), herbal reme Coverage: Global Endpoints: • herb ($0.12): Herb profile • remedy ($0.10): Cross-cultural remedy lookup • ingredient ($0.10): Supplement decoder • interaction ($0.10): Herb-drug interaction checker • skin ($0.08): Natural skincare ingredient • tradition ($0.08): Healing tradition deep dive • practitioner ($0.08): Practitioner guide • cannabis ($0.12): Cannabis and cannabinoid intelligence. It is categorised as a Read tool in the Pulsenetwork MCP Server, which means it retrieves data without modifying state.

What parameters does herbapulse accept? +

herbapulse accepts 12 parameters: drug, herb, lang, type, topic, action, concern, product, compound, location, condition, tradition. Required: action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on herbapulse? +

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

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

Can I rate-limit herbapulse? +

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

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

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