Greet the user
AI agents call greet as a supporting operation in Server Pdf workflows.
Greeting a user is a purely communicative/presentational action with no data retrieval, modification, execution, or financial implications. It does not read, write, or alter any data. Confidence is slightly reduced because the description is minimal and the tool appears in a PDF server context which is unusual for a greeting tool.
From the tool's definition Tool name is 'greet' and description says 'Greet the user'
Attacks that exploit this kind of access
Greet the user. It is categorised as a Other tool in the Server Pdf MCP Server, which means it performs auxiliary operations.
Register the Server Pdf MCP server in PolicyLayer and add a rule for greet: 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 Server Pdf. Nothing to install.
greet is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the greet 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 greet. 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.
greet is provided by the Server Pdf MCP server (@modelcontextprotocol/server-pdf). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →