Get page count and physical sheet information for a file before printing. Pre-renders the file (if needed) and returns page metadata including page count and physical sheets required.
AI agents call get_page_meta to retrieve information from MCP Printer Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns metadata about a file's page structure. It has no side effects beyond pre-rendering (which is necessary to gather the requested information) and does not modify, delete, execute commands, or trigger financial operations. It fits the Read category definition: 'retrieves or queries data; no side effects'.
From the tool's definition Tool name 'get_page_meta' and description state it 'returns page metadata including page count and physical sheets required' — it retrieves information about a file without modifying, deleting, or executing any operations.
Documented attack patterns abuse exactly the kind of access get_page_meta gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Printer Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_page_meta:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_meta": {}
}
}get_page_meta 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.
Get page count and physical sheet information for a file before printing. Pre-renders the file (if needed) and returns page metadata including page count and physical sheets required. It is categorised as a Read tool in the MCP Printer Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Printer Server MCP server in PolicyLayer and add a rule for get_page_meta: 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 MCP Printer Server. Nothing to install.
get_page_meta 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 get_page_meta 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 get_page_meta. 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.
get_page_meta is provided by the MCP Printer Server MCP server (steveclarke/mcp-printer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Printer 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.
8 MCP Printer Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.