Health check for Axure MCP server runtime.
AI agents call axure_health to retrieve information from Axure without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Health checks are read-only operations that retrieve status information about system components. They have no side effects, do not modify data, do not execute external commands, and do not alter system state. This is a standard operational diagnostic tool with minimal security risk.
From the tool's definition Tool is named 'axure_health' and performs a 'health check for Axure MCP server runtime', which is a diagnostic operation that queries server status without modifying, executing external operations, or affecting data.
Documented attack patterns abuse exactly the kind of access axure_health gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Axure, and nothing reaches the server without passing your rules. This is the rule we recommend for axure_health:
{
"version": "1",
"default": "deny",
"tools": {
"axure_health": {}
}
}axure_health 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.
Health check for Axure MCP server runtime. It is categorised as a Read tool in the Axure MCP Server, which means it retrieves data without modifying state.
Register the Axure MCP server in PolicyLayer and add a rule for axure_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 Axure. Nothing to install.
axure_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 axure_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 axure_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.
axure_health is provided by the Axure MCP server (six-ben/axure-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Axure, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Axure tools catalogued and risk-classified — across an index of 43,000+ MCP servers.