This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/twilio-get-message.md
What twilio_get_message does on UnClick
AI agents call twilio_get_message to retrieve information from UnClick 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 |
|---|---|---|---|
auth_token | string | Yes | |
account_sid | string | Yes | |
message_sid | string | Yes |
Parameters from the server's own tool schema.
Why twilio_get_message is rated Low
This tool retrieves/queries a single message from Twilio using its SID (message identifier). It has no side effects on the message itself. However, medium severity is appropriate because retrieving messages could expose sensitive communication data (PII, authentication tokens, business-critical information) if an agent queries messages it shouldn't access, though the risk is contingent on access controls and what…
From the tool's definition Tool name 'twilio_get_message' and description 'Get a single Twilio message by SID' indicate retrieval of existing message data without modification or deletion.
Attacks that exploit this kind of access
The rule that runs twilio_get_message safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For twilio_get_message, this is the rule to start with:
twilio_get_message is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every twilio_get_message call is checked against it from then on.
Questions about twilio_get_message
Get a single Twilio message by SID. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
twilio_get_message accepts 3 parameters: auth_token, account_sid, message_sid. Required: auth_token, account_sid, message_sid. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for twilio_get_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 UnClick. Nothing to install.
twilio_get_message is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the twilio_get_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 twilio_get_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.
twilio_get_message is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue