Low Risk

check_trust_score

check_trust_score

How to control check_trust_score ↓

What check_trust_score does on Semantic Metrics Modeling Assistant

AI agents call check_trust_score to retrieve information from Semantic Metrics Modeling Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why check_trust_score needs a policy

The tool name and context indicate this retrieves or checks existing trust score data without modifying, deleting, or executing arbitrary operations. Trust scoring in a semantic metrics system is a read-only inspection function.

From the tool's definition Tool name 'check_trust_score' is a query/inspection operation that retrieves trust score metadata. Sibling tool 'calculate_trust_score_enhanced_tool' performs computations, but 'check_trust_score' appears to be the read counterpart.

Documented attack patterns abuse exactly the kind of access check_trust_score gives an agent:

How to control check_trust_score

PolicyLayer is an MCP gateway — it sits between your AI agents and Semantic Metrics Modeling Assistant, and nothing reaches the server without passing your rules. This is the rule we recommend for check_trust_score:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_trust_score": {}
  }
}

check_trust_score is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Semantic Metrics Modeling Assistant — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about check_trust_score

What does the check_trust_score tool do? +

check_trust_score. It is categorised as a Read tool in the Semantic Metrics Modeling Assistant MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_trust_score? +

Register the Semantic Metrics Modeling Assistant MCP server in PolicyLayer and add a rule for check_trust_score: 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 Semantic Metrics Modeling Assistant. Nothing to install.

What risk level is check_trust_score? +

check_trust_score is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_trust_score? +

Yes. Add a rate_limit block to the check_trust_score 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.

How do I block check_trust_score completely? +

Set action: deny in the PolicyLayer policy for check_trust_score. 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.

What MCP server provides check_trust_score? +

check_trust_score is provided by the Semantic Metrics Modeling Assistant MCP server (jkelleman/semantic-metrics-modeling-assistant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Semantic Metrics Modeling Assistant tool call.

Start from Semantic Metrics Modeling Assistant, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

11 Semantic Metrics Modeling Assistant tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.