Check the reputation of a domain based on aggregated scan history.
AI agents call reputation_check to retrieve information from SkillAudit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
domain | string | — | Domain to check (e.g. example.com) |
Parameters from the server's own tool schema.
This tool retrieves and queries reputation data from aggregated scan history. It performs a lookup/retrieval action characteristic of Read category tools (search, list, get, fetch). There is no indication of creation, modification, deletion, code execution, financial activity, or irreversible changes.
From the tool's definition Tool is named 'reputation_check' and described as 'Check the reputation of a domain based on aggregated scan history'—a purely informational lookup operation with no side effects, data modification, or code execution.
Documented attack patterns abuse exactly the kind of access reputation_check gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SkillAudit, and nothing reaches the server without passing your rules. This is the rule we recommend for reputation_check:
{
"version": "1",
"default": "deny",
"tools": {
"reputation_check": {}
}
}reputation_check is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check the reputation of a domain based on aggregated scan history. It is categorised as a Read tool in the SkillAudit MCP Server, which means it retrieves data without modifying state.
reputation_check accepts 1 parameter: domain. The full parameter table on this page comes from the server's own tool schema.
Register the SkillAudit MCP server in PolicyLayer and add a rule for reputation_check: 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 SkillAudit. Nothing to install.
reputation_check 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 reputation_check 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 reputation_check. 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.
reputation_check is provided by the SkillAudit MCP server (megamind-0x/skillaudit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SkillAudit, 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.
4 SkillAudit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.