daily_plan

Plan TODAY: pick the day

SERVERFeatureBoard SOURCEhttps://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ai-featureboard-featureboard/daily-plan.md

WHAT IT DOES

What daily_plan does on FeatureBoard

AI agents call daily_plan to retrieve information from FeatureBoard without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why daily_plan is rated Low

The description implies a planning or scheduling read operation — selecting which day to plan. There is no indication of data modification, deletion, or execution of code. However, the description is vague, which lowers confidence. Based on available context, this most likely retrieves or organizes planning data for a given day.

From the tool's definition 'Plan TODAY: pick the day' — suggests selecting/viewing a daily plan

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs daily_plan safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FeatureBoard, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For daily_plan, this is the rule to start with:

daily_plan Allowed

daily_plan is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "daily_plan": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FeatureBoard, apply this rule, and every daily_plan call is checked against it from then on.

FAQ

Questions about daily_plan

What does the daily_plan tool do? +

Plan TODAY: pick the day. It is categorised as a Read tool in the FeatureBoard MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on daily_plan? +

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

What risk level is daily_plan? +

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

Can I rate-limit daily_plan? +

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

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

daily_plan is provided by the FeatureBoard MCP server (https://github.com/valentil/featureboard-mcp/releases/download/v0.7/featureboard.plugin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FeatureBoard, and thousands of servers like it.

This server

All 215 FeatureBoard tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →