メインメッセージとして hello world を返す開発者向けツール
AI agents call dev-helloworld to retrieve information from Local Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool merely returns a greeting message to developers. It performs no queries, does not create or modify data, does not execute code or commands, does not delete anything, and involves no financial transactions. This is a benign Read operation that retrieves static content.
From the tool's definition Tool description indicates it "returns hello world as a main message" for developers. This is a simple informational tool that retrieves and displays a static message with no side effects, data modification, or external operations.
Attacks that exploit this kind of access
メインメッセージとして hello world を返す開発者向けツール. It is categorised as a Read tool in the Local Context MCP Server, which means it retrieves data without modifying state.
Register the Local Context MCP server in PolicyLayer and add a rule for dev-helloworld: 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 Local Context. Nothing to install.
dev-helloworld 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 dev-helloworld 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 dev-helloworld. 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.
dev-helloworld is provided by the Local Context MCP server (obaratch/local-context-mcp). 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 →