Look up the trust score for any MCP server by URL or npm package name. Returns score, grade, findings summary, and certification status.
Part of the Mcp Shield server.
Free to start. No card required.
AI agents call check_trust to retrieve information from Mcp Shield 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 check_trust 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": {
"check_trust": {}
}
}See the full Mcp Shield policy for all 4 tools.
These attack patterns abuse exactly the kind of access check_trust 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.
Look up the trust score for any MCP server by URL or npm package name. Returns score, grade, findings summary, and certification status.. It is categorised as a Read tool in the Mcp Shield MCP Server, which means it retrieves data without modifying state.
Register the Mcp Shield MCP server in PolicyLayer and add a rule for check_trust: 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 Mcp Shield. Nothing to install.
check_trust 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 check_trust 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 check_trust. 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.
check_trust is provided by the Mcp Shield MCP server (https://mcp.craftedtrust.com/api/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Mcp Shield 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.