Get the current user
AI agents call get_storyline_feed 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 user profile or feed data without side effects. It is a straightforward read operation that accesses existing information. The minimal scope (single user context) and read-only nature warrant low severity. Confidence is high despite the terse description because the name and server context clearly indicate data retrieval.
From the tool's definition Tool name and description indicate it retrieves current user information ('Get the current user'). The server context describes functionality for 'browsing communities, searching posts, reading conversations' with sibling tools including get_communities,…
Attacks that exploit this kind of access
Get the current user. 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_storyline_feed: 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_storyline_feed 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_storyline_feed 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_storyline_feed. 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_storyline_feed 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 →