filter_by_date

Filter entries by date range

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

What filter_by_date does on ContextForge MCP Gateway

AI agents call filter_by_date 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 filter_by_date needs a policy

This tool retrieves or queries data by applying a date-range filter—a purely read operation with no side effects, no data creation, modification, or deletion. It returns a filtered view of existing entries. The low severity reflects minimal risk: even if misused by an AI agent, filtering operations cannot corrupt or compromise data.

From the tool's definition Tool name 'filter_by_date' and description 'Filter entries by date range' indicate a query/filtering operation with no modification or deletion of data.

Questions about filter_by_date

What does the filter_by_date tool do? +

Filter entries by date range. 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 filter_by_date? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for filter_by_date: 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 filter_by_date? +

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

Can I rate-limit filter_by_date? +

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

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

filter_by_date 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.