New PolicyLayer is now the system of record for AI agent authority. Never answer your agent twice

check_api_health

Maps to GET /health. Returns service availability. Use to confirm the API is responsive before attempting operations.

SERVERSwapwizard SOURCE@swapwizard/mcp-server
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/defire-business-swapwizard-mcp/check-api-health.md

What check_api_health does on Swapwizard

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

Why check_api_health is rated Low

This is a simple status query that retrieves service availability metadata. It has no side effects, does not move funds, execute transactions, or modify state. It is purely informational and falls squarely within the Read category.

From the tool's definition Tool name 'check_api_health' and description 'Maps to GET /health. Returns service availability' indicate a read-only health check endpoint that retrieves status information without modifying or executing any operations.

Questions about check_api_health

What does the check_api_health tool do? +

Maps to GET /health. Returns service availability. Use to confirm the API is responsive before attempting operations. It is categorised as a Read tool in the Swapwizard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_api_health? +

Register the Swapwizard MCP server in PolicyLayer and add a rule for check_api_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 Swapwizard. Nothing to install.

What risk level is check_api_health? +

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

Can I rate-limit check_api_health? +

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

How do I block check_api_health completely? +

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

What MCP server provides check_api_health? +

check_api_health is provided by the Swapwizard MCP server (@swapwizard/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Swapwizard, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Swapwizard's. Pull the full record:

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.