get_facebook_stories
AI agents call get_facebook_stories to retrieve information from Mcp Metricool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_' prefix and context of a social media metrics/analytics API strongly suggest this tool queries and retrieves Facebook Stories data. No write, execute, destructive, or financial operations are implied. Confidence is not higher because the tool description is empty, leaving some ambiguity, but the naming pattern and server purpose are clear indicators of a read operation.
From the tool's definition Tool name 'get_facebook_stories' with sibling tools all named 'get_*' (get_best_time_to_post, get_bluesky_posts, get_brands, get_facebook_posts, etc.) and server description stating 'interact with Metricool API for social media metrics, campaign data, and…
Attacks that exploit this kind of access
get_facebook_stories. It is categorised as a Read tool in the Mcp Metricool MCP Server, which means it retrieves data without modifying state.
Register the Mcp Metricool MCP server in PolicyLayer and add a rule for get_facebook_stories: 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 Metricool. Nothing to install.
get_facebook_stories 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_facebook_stories 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_facebook_stories. 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_facebook_stories is provided by the Mcp Metricool MCP server (namdzmaso02/mcp-metricool). 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 →