AI agents call paserver_check_connection to retrieve information from Claude Pascal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name suggests a read/status-check operation (verifying connectivity to PAServer, Delphi's remote deployment server). No description is provided to confirm side effects. Given the 'check' verb and context of the server, this is most likely a read-only connectivity probe. Confidence is reduced due to empty description.
From the tool's definition Tool name: 'paserver_check_connection' — implies checking/verifying a connection status; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access paserver_check_connection gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Pascal MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for paserver_check_connection:
{
"version": "1",
"default": "deny",
"tools": {
"paserver_check_connection": {}
}
}paserver_check_connection 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.
paserver_check_connection. It is categorised as a Read tool in the Claude Pascal MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Claude Pascal MCP Server MCP server in PolicyLayer and add a rule for paserver_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 Claude Pascal MCP Server. Nothing to install.
paserver_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 paserver_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 paserver_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.
paserver_check_connection is provided by the Claude Pascal MCP Server MCP server (tina4stack/claude-pascal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Pascal MCP Server, 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.
53 Claude Pascal MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.