herbapulse

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

Low RISK CLASS

Category Read

Parameters 121 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What herbapulse does on Pulsenetwork

AI agents call herbapulse 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
`drug`	string	—	drug
`herb`	string	—	herb
`lang`	string	—	lang
`type`	string	—	naturopath \| herbalist \| tcm \| ayurveda \| homeopath \| integrative-md
`focus`	string	—	Comma-separated: sleep, digestion, immune, first-aid, skin, stress
`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 \| protocol \| apothecary
`budget`	string	—	starter \| standard (default) \| complete
`remedy`	string	—	Specific remedy to compile, e.g. castor oil pack, fire cider
`concern`	string	—	anti-aging \| acne \| hydration \| sensitivity
`product`	string	—	product
`audience`	string	—	adult (default) \| child \| pregnancy — tightens safety rails

Parameters from the server's own tool schema.

RISK

Why herbapulse is rated Low

Retrieves herbal information and remedy data without creating, modifying, or executing external operations or financial transactions.

From the tool's definition centralized natural-remedies layer, herb profiles, PubMed-grounded, educational, never medical advice

Risk signalsHigh parameter count (19 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs herbapulse 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 herbapulse, this is the rule to start with:

herbapulse Allowed

herbapulse 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": {
    "herbapulse": {}
  }
}

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 herbapulse call is checked against it from then on.

FAQ

Questions about herbapulse

What does the herbapulse tool do? +

HerbaPulse: The centralized natural-remedies layer — 10 endpoints. Home remedy protocol compiler (practical preparations with real ratios, honest evidence labels, safety rails, buyable ingredient lists), home apothecary kit builder (household-matched stocked cabinet), PubMed-grounded herb profiles, herb-drug interaction checker, supplement decoder, natural skincare, traditional medicine guides (Ayurveda, TCM), practitioner guidance, cannabis intelligence. Educational, never medical advice. 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 • protocol ($0.15): Home remedy protocol compiler • apothecary ($0.25): Home apothecary kit builder. 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, focus, topic, action, budget, remedy, concern, product, audience. 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.

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 →