Get recent messages across ALL communities. Use this to summarize what
AI agents call get_recent_messages to retrieve information from Mcp Viva Engage without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves recent messages for viewing purposes. It has no side effects, creates no new data, executes no commands, and causes no irreversible changes. Blast radius is minimal—worst case is information disclosure of already-accessible messages within the user's Viva Engage scope.
From the tool's definition Tool name 'get_recent_messages' and description 'Get recent messages across ALL communities' indicate retrieval of existing data without modification. The verb 'get' and context of 'summarize' confirm read-only operation.
Attacks that exploit this kind of access
Get recent messages across ALL communities. Use this to summarize what. It is categorised as a Read tool in the Mcp Viva Engage MCP Server, which means it retrieves data without modifying state.
Register the Mcp Viva Engage MCP server in PolicyLayer and add a rule for get_recent_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 Viva Engage. Nothing to install.
get_recent_messages 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 get_recent_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.
Set action: deny in the PolicyLayer policy for get_recent_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.
get_recent_messages is provided by the Mcp Viva Engage MCP server (pranav4186/mcp-viva-engage). 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 →