The unit tests (code examples) for HMR. Always call learn-hmr-basics and view-hmr-core-sources to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You sh...
Part of the Hmr server.
Free to start. No card required.
AI agents call view-hmr-unit-tests to retrieve information from Hmr without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though view-hmr-unit-tests only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"view-hmr-unit-tests": {}
}
}See the full Hmr policy for all 3 tools.
These attack patterns abuse exactly the kind of access view-hmr-unit-tests gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
The unit tests (code examples) for HMR. Always call learn-hmr-basics and view-hmr-core-sources to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.. It is categorised as a Read tool in the Hmr MCP Server, which means it retrieves data without modifying state.
Register the Hmr MCP server in PolicyLayer and add a rule for view-hmr-unit-tests: 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 Hmr. Nothing to install.
view-hmr-unit-tests 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 view-hmr-unit-tests 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 view-hmr-unit-tests. 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.
view-hmr-unit-tests is provided by the Hmr MCP server (https://pyth-on-line.promplate.dev/hmr/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Hmr tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.