AI agents call related_signatures to retrieve information from Novyx without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'related_signatures' most naturally suggests querying or retrieving signature-related data (likely cryptographic signatures, audit signatures, or approval signatures given the governance context). No action words like 'create', 'delete', 'execute', or 'approve' appear in the name. However, the empty description reduces confidence; it could theoretically be something different.
From the tool's definition Tool name 'related_signatures' suggests retrieval of signature metadata or records. Description is empty, limiting direct evidence. Tool is part of a governance/audit system (novyx-mcp) where reading audit trails and signatures is expected behavior.
Documented attack patterns abuse exactly the kind of access related_signatures gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Novyx, and nothing reaches the server without passing your rules. This is the rule we recommend for related_signatures:
{
"version": "1",
"default": "deny",
"tools": {
"related_signatures": {}
}
}related_signatures 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.
related_signatures. It is categorised as a Read tool in the Novyx MCP Server, which means it retrieves data without modifying state.
Register the Novyx MCP server in PolicyLayer and add a rule for related_signatures: 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 Novyx. Nothing to install.
related_signatures 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 related_signatures 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 related_signatures. 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.
related_signatures is provided by the Novyx MCP server (novyxlabs/novyx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 120 Novyx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
120 Novyx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.