Medium Risk

me.add_evidence

Authenticated — append a free-text evidence note to a specific stage in the caller's active course. Notes record concrete implementation observations, decisions, or artefacts that demonstrate progress through a Blueprint principle (e.g. how a delegation boundary was implemented, what approval flo...

Part of the AI Design Blueprint server.

me.add_evidence can modify AI Design Blueprint data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE AI DESIGN BLUEPRINT →

Free to start. No card required.

AI agents use me.add_evidence to create or modify resources in AI Design Blueprint. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call me.add_evidence repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach AI Design Blueprint.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "me.add_evidence": {
      "limits": [
        {
          "counter": "me.add_evidence_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full AI Design Blueprint policy for all 24 tools.

Get this rule live on your own AI Design Blueprint server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AI DESIGN BLUEPRINT →

View all 24 tools →

These attack patterns abuse exactly the kind of access me.add_evidence gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so me.add_evidence only ever does what you allow.

SECURE AI DESIGN BLUEPRINT →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the me.add_evidence tool do? +

Authenticated — append a free-text evidence note to a specific stage in the caller's active course. Notes record concrete implementation observations, decisions, or artefacts that demonstrate progress through a Blueprint principle (e.g. how a delegation boundary was implemented, what approval flow was chosen and why). Persisted as UserStageEvidence rows scoped to (user_id, course_slug, stage_slug). WHEN TO CALL: AFTER the user has articulated something concrete they have built, observed, or decided — not to capture intent or speculation. Pair with me.coaching_context to close evidence gaps. WHEN NOT TO CALL: to log every conversation turn; to record planning, ideas, or todos; on behalf of another user; without the user's awareness (they should know their progress is being recorded). BEHAVIOR: write-only, single insert. Auth: Bearer <token> (Firebase ID token, any plan). UK/EU residency. Notes are visible only to the owning user and are surfaced on me.learning_path / me.coaching_context. Confirms the stage_slug + course_slug pair in the response so the user can see which stage was credited.. It is categorised as a Write tool in the AI Design Blueprint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on me.add_evidence? +

Register the AI Design Blueprint MCP server in PolicyLayer and add a rule for me.add_evidence: 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 AI Design Blueprint. Nothing to install.

What risk level is me.add_evidence? +

me.add_evidence is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit me.add_evidence? +

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

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

me.add_evidence is provided by the AI Design Blueprint MCP server (https://aidesignblueprint.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AI Design Blueprint tool call.

Deterministic rules across all 24 AI Design Blueprint tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.