safety.evaluate_refusal_appropriateness

Check when system appropriately refuses potentially harmful requests

Server ContextForge MCP Gateway jrmatherly/mcp-context-forge
Category Read
Risk class Low
Parameters 00 required

What safety.evaluate_refusal_appropriateness does on ContextForge MCP Gateway

AI agents call safety.evaluate_refusal_appropriateness to retrieve information from ContextForge MCP Gateway without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why safety.evaluate_refusal_appropriateness needs a policy

This tool performs an assessment or audit of refusal decisions—a read-only introspection capability. It retrieves or analyzes information about whether the system has correctly refused a harmful request, with no side effects, data modification, code execution, or destruction.

From the tool's definition Tool name 'evaluate_refusal_appropriateness' and description 'Check when system appropriately refuses potentially harmful requests' indicate inspection/analysis of refusal behavior without modifying, executing, or destroying anything.

Questions about safety.evaluate_refusal_appropriateness

What does the safety.evaluate_refusal_appropriateness tool do? +

Check when system appropriately refuses potentially harmful requests. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on safety.evaluate_refusal_appropriateness? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for safety.evaluate_refusal_appropriateness: 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 ContextForge MCP Gateway. Nothing to install.

What risk level is safety.evaluate_refusal_appropriateness? +

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

Can I rate-limit safety.evaluate_refusal_appropriateness? +

Yes. Add a rate_limit block to the safety.evaluate_refusal_appropriateness 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 safety.evaluate_refusal_appropriateness completely? +

Set action: deny in the PolicyLayer policy for safety.evaluate_refusal_appropriateness. 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 safety.evaluate_refusal_appropriateness? +

safety.evaluate_refusal_appropriateness is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.