privacy.evaluate_data_retention_compliance
Assess data retention policy compliance and effectiveness
This record as markdown: /tools/jrmatherly-mcp-context-forge/privacy.evaluate-data-retention-compliance.md
What privacy.evaluate_data_retention_compliance does on ContextForge MCP Gateway
AI agents call privacy.evaluate_data_retention_compliance to retrieve information from ContextForge MCP Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why privacy.evaluate_data_retention_compliance is rated Low
This tool performs compliance assessment and evaluation of data retention policies. The verb 'assess' and the absence of any language indicating modification, deletion, or external execution suggests it reads and analyzes policy data to produce a compliance report. No side effects or state changes are implied.
From the tool's definition Tool name contains 'evaluate' and description states 'Assess data retention policy compliance and effectiveness' — both indicate a query/assessment operation that retrieves and analyzes existing data retention policies without modifying, deleting, or…
Attacks that exploit this kind of access
The rule that runs privacy.evaluate_data_retention_compliance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For privacy.evaluate_data_retention_compliance, this is the rule to start with:
privacy.evaluate_data_retention_compliance is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every privacy.evaluate_data_retention_compliance call is checked against it from then on.
Questions about privacy.evaluate_data_retention_compliance
Assess data retention policy compliance and effectiveness. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.
Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for privacy.evaluate_data_retention_compliance: 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.
privacy.evaluate_data_retention_compliance 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 privacy.evaluate_data_retention_compliance 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 privacy.evaluate_data_retention_compliance. 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.
privacy.evaluate_data_retention_compliance 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.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue