Load one saved signature by name. Returns the style, display name, and for image signatures a preview data URL so the viewer can render the selected asset on demand.
AI agents call load_signature to retrieve information from PDF Tools without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns metadata about a previously saved signature (style, display name, preview URL). It performs a query/read operation on stored signature data without creating, modifying, deleting, or executing any operations. The output is informational only, making it a classic Read category tool with low risk of misuse.
From the tool's definition Tool name 'load_signature' and description 'Load one saved signature by name. Returns the style, display name, and for image signatures a preview data URL' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access load_signature gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PDF Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for load_signature:
{
"version": "1",
"default": "deny",
"tools": {
"load_signature": {}
}
}load_signature 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.
Load one saved signature by name. Returns the style, display name, and for image signatures a preview data URL so the viewer can render the selected asset on demand. It is categorised as a Read tool in the PDF Tools MCP Server, which means it retrieves data without modifying state.
Register the PDF Tools MCP server in PolicyLayer and add a rule for load_signature: 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 PDF Tools. Nothing to install.
load_signature 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 load_signature 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 load_signature. 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.
load_signature is provided by the PDF Tools MCP server (open-document-alliance/pdf-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 PDF Tools tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 PDF Tools tools catalogued and risk-classified — across an index of 42,500+ MCP servers.