ligolo_certificate_fingerprint

Get the certificate fingerprint for agent verification

Server Ligolo-ng MCP Server schwarztim/sec-ligolo-ng-mcp
Category Read
Risk class Low
Parameters 00 required

What ligolo_certificate_fingerprint does on Ligolo-ng MCP Server

AI agents call ligolo_certificate_fingerprint to retrieve information from Ligolo-ng MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why ligolo_certificate_fingerprint needs a policy

This tool retrieves certificate fingerprint information for verification purposes. It performs a read-only query operation with no side effects, data modification, code execution, or destructive actions. The fingerprint is informational data used for security verification, not a capability that triggers external operations or modifies state.

From the tool's definition Tool name 'ligolo_certificate_fingerprint' and description 'Get the certificate fingerprint for agent verification' indicate a retrieval operation that queries and returns certificate fingerprint data without modification.

Questions about ligolo_certificate_fingerprint

What does the ligolo_certificate_fingerprint tool do? +

Get the certificate fingerprint for agent verification. It is categorised as a Read tool in the Ligolo-ng MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on ligolo_certificate_fingerprint? +

Register the Ligolo-ng MCP Server MCP server in PolicyLayer and add a rule for ligolo_certificate_fingerprint: 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 Ligolo-ng MCP Server. Nothing to install.

What risk level is ligolo_certificate_fingerprint? +

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

Can I rate-limit ligolo_certificate_fingerprint? +

Yes. Add a rate_limit block to the ligolo_certificate_fingerprint 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 ligolo_certificate_fingerprint completely? +

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

ligolo_certificate_fingerprint is provided by the Ligolo-ng MCP Server MCP server (schwarztim/sec-ligolo-ng-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.