Check server status and required env vars.
AI agents call health to retrieve information from LinkedIn Poster without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and reports on the server's health status and environment variable configuration. It has no side effects, does not post or modify any data, and cannot cause harm if misused.
From the tool's definition Check server status and required env vars.
Attacks that exploit this kind of access
Check server status and required env vars. It is categorised as a Read tool in the LinkedIn Poster MCP Server, which means it retrieves data without modifying state.
Register the LinkedIn Poster MCP server in PolicyLayer and add a rule for health: 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 LinkedIn Poster. Nothing to install.
health 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 health 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 health. 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.
health is provided by the LinkedIn Poster MCP server (urfanazad/posterlinkedin). 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 →