Check if the JEB plugin is running
AI agents call check_connection to retrieve information from APK Security Guard MCP Suite without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that simply verifies connectivity to the JEB plugin. It retrieves status information with no side effects, no code execution, no data modification, and no destructive capability. It represents basic diagnostic monitoring typical of health-check endpoints.
From the tool's definition Tool name 'check_connection' and description 'Check if the JEB plugin is running' indicate a simple status check that queries the state of a service without modifying, executing operations, or affecting data.
Attacks that exploit this kind of access
Check if the JEB plugin is running. It is categorised as a Read tool in the APK Security Guard MCP Suite MCP Server, which means it retrieves data without modifying state.
Register the APK Security Guard MCP Suite MCP server in PolicyLayer and add a rule for check_connection: 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 APK Security Guard MCP Suite. Nothing to install.
check_connection 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 check_connection 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 check_connection. 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.
check_connection is provided by the APK Security Guard MCP Suite MCP server (zmbcen/apk-security-guard-mcp-suite). 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 →