engine_verify
Verify API credentials by making lightweight test calls to each service. All verification calls are read-only and non-destructive. Example: engine_verify({ services: [
This record as markdown: /tools/io-github-0nork-0nmcp/engine-verify.md
What engine_verify does on 0nmcp
AI agents call engine_verify to retrieve information from 0nmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why engine_verify is rated Low
This tool performs authentication/credential verification via read-only test calls to services. It retrieves information to confirm credentials work but does not modify, execute code, delete data, or commit financial obligations. The explicit statement that calls are 'read-only and non-destructive' confirms the Read category.
From the tool's definition Tool description states 'All verification calls are read-only and non-destructive.' The function name 'engine_verify' and its purpose to validate credentials through test calls indicate data retrieval only.
Attacks that exploit this kind of access
The rule that runs engine_verify safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 0nmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For engine_verify, this is the rule to start with:
engine_verify 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 0nmcp, apply this rule, and every engine_verify call is checked against it from then on.
Questions about engine_verify
Verify API credentials by making lightweight test calls to each service. All verification calls are read-only and non-destructive. Example: engine_verify({ services: [. It is categorised as a Read tool in the 0nmcp MCP Server, which means it retrieves data without modifying state.
Register the 0n MCP server in PolicyLayer and add a rule for engine_verify: 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 0nmcp. Nothing to install.
engine_verify 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 engine_verify 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 engine_verify. 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.
engine_verify is provided by the 0n MCP server (0nmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 0n, and thousands of servers like it.
This server
Across the catalogue