Retrieve likes and comments for posts in a specific watchlist. Use to analyze engagement activity, build reports, or power dashboards. Returns interactions with full post objects, pagination with like/comment totals, and a 7-day graph.
AI agents call get_interactions to retrieve information from Outx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_interactions retrieves historical engagement metrics (likes and comments) from existing posts in a watchlist. It has no side effects, does not modify data, and does not execute external code or trigger actions. This is a straightforward data retrieval operation.
From the tool's definition Tool description uses 'Retrieve' and 'analyze engagement activity, build reports, or power dashboards' — operations that query and return data without modification. No create, update, delete, or execute operations are mentioned.
Attacks that exploit this kind of access
Retrieve likes and comments for posts in a specific watchlist. Use to analyze engagement activity, build reports, or power dashboards. Returns interactions with full post objects, pagination with like/comment totals, and a 7-day graph. It is categorised as a Read tool in the Outx MCP Server, which means it retrieves data without modifying state.
Register the Outx MCP server in PolicyLayer and add a rule for get_interactions: 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 Outx. Nothing to install.
get_interactions 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_interactions 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_interactions. 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_interactions is provided by the Outx MCP server (outx-mcp-server). 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 →