Check if the server is running and can access its resources
AI agents call health_check to retrieve information from OSP Marketing Tools MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a standard health/status check operation that retrieves information about server availability and resource accessibility. It has no side effects, does not execute code, does not modify data, and does not delete anything. It is purely informational, making it a Read category tool with low severity.
From the tool's definition Tool name 'health_check' and description 'Check if the server is running and can access its resources' indicate a read-only diagnostic operation that queries server status without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access health_check gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OSP Marketing Tools MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for health_check:
{
"version": "1",
"default": "deny",
"tools": {
"health_check": {}
}
}health_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if the server is running and can access its resources. It is categorised as a Read tool in the OSP Marketing Tools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OSP Marketing Tools MCP Server MCP server in PolicyLayer and add a rule for health_check: 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 OSP Marketing Tools MCP Server. Nothing to install.
health_check 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_check 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_check. 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_check is provided by the OSP Marketing Tools MCP Server MCP server (open-strategy-partners/osp_marketing_tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 6 OSP Marketing Tools MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
6 OSP Marketing Tools MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.