New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_messages

List all SMS messages received in this session without consuming the OTP. Use this to inspect raw messages or check if an SMS arrived before calling wait_for_otp. Does NOT mark the OTP as consumed.

SERVERMcp SOURCEhttps://mcp.agentsim.dev/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/dev-agentsim-mcp/get-messages.md

What get_messages does on Mcp

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

ParameterTypeRequiredDescription
input object Yes

Parameters from the server's own tool schema.

Why get_messages is rated Low

This tool retrieves and queries SMS message data without creating, modifying, or deleting any information. It performs a passive inspection operation with no irreversible effects. The explicit note that it does not consume the OTP confirms no state changes occur. This is a clear Read operation with minimal security risk unless exposed messages contain highly sensitive credentials, warranting only 'low' severity.

From the tool's definition Tool name is 'get_messages' and description explicitly states it 'List[s] all SMS messages' and 'Does NOT mark the OTP as consumed', indicating retrieval without modification or side effects.

Questions about get_messages

What does the get_messages tool do? +

List all SMS messages received in this session without consuming the OTP. Use this to inspect raw messages or check if an SMS arrived before calling wait_for_otp. Does NOT mark the OTP as consumed. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.

What parameters does get_messages accept? +

get_messages accepts 1 parameter: input. Required: input. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_messages? +

Register the MCP server in PolicyLayer and add a rule for get_messages: 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 Mcp. Nothing to install.

What risk level is get_messages? +

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

Can I rate-limit get_messages? +

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

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

get_messages is provided by the MCP server (https://mcp.agentsim.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on , and thousands of servers like it.

This server

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.