Send a message to a Teladoc provider
AI agents use send_message to create or update resources in Teladoc MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Teladoc MCP Server environment.
The tool creates new message records in the Teladoc system, modifying the state of patient-provider communications. This is categorized as Write rather than Read (it modifies, not retrieves), Execute (no arbitrary code execution), Destructive (messages are not irreversibly deleted by sending them), or Financial (no money movement).
From the tool's definition Tool name 'send_message' and description 'Send a message to a Teladoc provider' indicate the tool creates/modifies communication data by posting a message to a healthcare provider within the telehealth platform.
Attacks that exploit this kind of access
Send a message to a Teladoc provider. It is categorised as a Write tool in the Teladoc MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Teladoc MCP Server MCP server in PolicyLayer and add a rule for send_message: 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 Teladoc MCP Server. Nothing to install.
send_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_message 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 send_message. 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.
send_message is provided by the Teladoc MCP Server MCP server (markswendsen-code/mcp-teladoc). 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 →