Get messages/posts in a specific Viva Engage community. Accepts community name (e.g.
AI agents call get_community_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 retrieves and queries existing messages from a community without creating, modifying, deleting, or executing actions. It is a pure read operation with minimal blast radius if misused—an agent could retrieve more data than intended, but no irreversible or harmful changes occur. Classified as Read with low severity.
From the tool's definition Tool name 'get_community_messages' and description 'Get messages/posts in a specific Viva Engage community' indicate data retrieval with no side effects. The server description emphasizes 'browsing communities' and 'reading conversations' as core functions.
Attacks that exploit this kind of access
Get messages/posts in a specific Viva Engage community. Accepts community name (e.g. 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_community_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_community_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_community_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_community_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_community_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 →