This record as markdown: /tools/frontmcp/parent-hello.md
What parent-hello does on Frontmcp
AI agents call parent-hello to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why parent-hello is rated Low
This is a simple utility tool that returns a greeting message. It retrieves or queries no sensitive data and produces no side effects—no data creation, modification, deletion, or external operations. It belongs in the Read category as the least risky classification, with low severity due to its trivial nature.
From the tool's definition Tool name 'parent-hello' and description 'A simple hello tool in the parent/root scope' indicate a greeting/informational function with no data modification, deletion, or external action execution.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs parent-hello safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For parent-hello, this is the rule to start with:
parent-hello is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every parent-hello call is checked against it from then on.
Questions about parent-hello
A simple hello tool in the parent/root scope. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for parent-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 Frontmcp. Nothing to install.
parent-hello 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 parent-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.
Set action: deny in the PolicyLayer policy for parent-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.
parent-hello is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue