hello

Say hello to someone

Server DocAgent vinnyfds/docagent
Category Read
Risk class Low
Parameters 00 required

What hello does on DocAgent

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

Why hello needs a policy

This is a benign greeting utility. It produces output (a greeting message) but does not query data, modify state, execute code, delete resources, or commit financial actions. Classified as Read (lowest impact) due to its purely informational nature. Low severity because misuse would have no meaningful blast radius.

From the tool's definition Tool name 'hello' and description 'Say hello to someone' indicate a simple greeting function with no data retrieval, modification, execution, or side effects.

Questions about hello

What does the hello tool do? +

Say hello to someone. It is categorised as a Read tool in the DocAgent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on hello? +

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

What risk level is hello? +

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

Can I rate-limit hello? +

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

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

hello is provided by the DocAgent MCP server (vinnyfds/docagent). 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.