Check if the AAS environment is ready for requests.
AI agents call is_healthy to retrieve information from Aas without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only status check of the AAS environment. It retrieves the health state without creating, modifying, deleting, or executing any operations on data or infrastructure. This is a harmless diagnostic query typical of health-check endpoints, with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name 'is_healthy' and description 'Check if the AAS environment is ready for requests' indicate a health/status query operation with no side effects.
Documented attack patterns abuse exactly the kind of access is_healthy gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Aas, and nothing reaches the server without passing your rules. This is the rule we recommend for is_healthy:
{
"version": "1",
"default": "deny",
"tools": {
"is_healthy": {}
}
}is_healthy 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 AAS environment is ready for requests. It is categorised as a Read tool in the Aas MCP Server, which means it retrieves data without modifying state.
Register the Aas MCP server in PolicyLayer and add a rule for is_healthy: 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 Aas. Nothing to install.
is_healthy 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 is_healthy 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 is_healthy. 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.
is_healthy is provided by the Aas MCP server (smartfactory-kl/aas-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Aas, 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.
25 Aas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.