linkedin_get_post_stats

Get analytics for a LinkedIn post: likes, comments, shares. Requires Community Management API authentication.

Server AmplifyrMCP supersaiyane/amplifyrmcp
Category Read
Risk class Low
Parameters 00 required

What linkedin_get_post_stats does on AmplifyrMCP

AI agents call linkedin_get_post_stats to retrieve information from AmplifyrMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why linkedin_get_post_stats needs a policy

This tool retrieves post analytics (metrics about engagement) from LinkedIn without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, making it a Read category tool with low severity since it only accesses non-sensitive aggregated metrics that the authenticated user should already have access to through normal LinkedIn functionality.

From the tool's definition Tool description explicitly states 'Get analytics for a LinkedIn post: likes, comments, shares' - a retrieval operation with no modification or side effects.

Questions about linkedin_get_post_stats

What does the linkedin_get_post_stats tool do? +

Get analytics for a LinkedIn post: likes, comments, shares. Requires Community Management API authentication. It is categorised as a Read tool in the AmplifyrMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on linkedin_get_post_stats? +

Register the Amplifyr MCP server in PolicyLayer and add a rule for linkedin_get_post_stats: 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 AmplifyrMCP. Nothing to install.

What risk level is linkedin_get_post_stats? +

linkedin_get_post_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit linkedin_get_post_stats? +

Yes. Add a rate_limit block to the linkedin_get_post_stats 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.

How do I block linkedin_get_post_stats completely? +

Set action: deny in the PolicyLayer policy for linkedin_get_post_stats. 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.

What MCP server provides linkedin_get_post_stats? +

linkedin_get_post_stats is provided by the Amplifyr MCP server (supersaiyane/amplifyrmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.