01 — OBSERVE
Observe the tool
Collect MCP metadata and tool schemas, then review them against static rules. Record both the observation's scope and what could not be checked.
TOOLGUARD · PREPAID API ACCESS
Before tools run,
check the trust.
Policy checks $0.001 each · scans $0.05 each.
No required monthly subscription. Minimum top-up $5.
Built for agent and gateway teams using MCP. Sign in with Google, register your service and policy, then add $5 with PayPal. Set spending limits before paid API use.
EXECUTION CHECK01 / GATE
Agent requestTool execution request
MCPToolGuard GateCHECK
Policy and approved observationsMatch
Signature and expiryVerify
Current key and receipt statusCheck
ALLOWExecute only on a verified allow result
Illustrative flow, not a real customer request result.
01Explicit policies
02Traceable evidence
03Block on failed verification
A CHECK BEFORE EVERY ACTION
Keep the evidence
behind every decision.
Connect observations of registered tools to your organization's policies.
Blocking requires SDK verification in your execution path.
02 — DECIDE
Check policy before execution
Compare approved baselines, observation validity, and organization policy. Distinguish allow, block, review required, and unknown outcomes.
03 — VERIFY
Verify before running
The SDK checks the signature, expiry, target binding, and current receipt status. Failed verification and unknown outcomes never become an allow.
KEEP THE BASELINE VISIBLE
Is yesterday's approved tool
still the same today?
Watch tracks changes to tool schemas and descriptions, then delivers changes for review through signed webhooks.
This is not a guarantee of safety or a certification that detects every vulnerability. It helps your team operate execution policies using observable evidence.
PREPAID USAGE PRICING
Start small.
Set a limit for every key.
One prepaid balance, with account and key limits.
$5 PayPal top-ups after service setup.
PAID POLICY CHECK
$0.001USD / check
Prepaid usage · no subscription required
Open account pageRegister your MCP service and policy on the account page.
Account access and payment availability are shown on the account page.
A focused first use case
- Billable unit
- One paid Gate policy check
- Eligible services
- Registered services with configured policy
- Available top-up
- $5 USD
- Spending controls
- Account and per-key daily limits
- Scans and monitoring
- Priced separately
- Human integration support
- Optional · quoted by scope
Complete service setup before adding funds. A policy check compares approved observations with configured policy; it is not a fresh scan, a full security audit, or a guarantee that a tool is safe. Funding alone does not onboard a service or approve its use.
OPTIONAL HUMAN INTEGRATION
Need help connecting
your execution path?
Integration support is optional and quoted after reviewing your scope. There is no mandatory integration package.
Contact: klisteninc@gmail.com
The existing ToolGuard API supports policy checks, observations, and signed verification. Service access and policies are arranged during onboarding. View the API specification ↗
- 01
Where do your tools run?
Identify your agent or gateway and the integration point for checks before execution.
- 02
What should be allowed?
Define the target MCP services, approval criteria, reviewers, and observation scope.
- 03
How will you decide what comes next?
Agree on next steps using block reasons, observed changes, false positives, and the support record.