refresh_project_context_docs · MCP SAPUI5 Server MCP

WHAT IT DOES

What refresh_project_context_docs does on MCP SAPUI5 Server

AI agents use refresh_project_context_docs to create or update resources in MCP SAPUI5 Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP SAPUI5 Server environment.

WHY IT NEEDS A POLICY

Why refresh_project_context_docs needs a policy

This tool updates/overwrites documentation and MCP context files in the project. It modifies existing files incrementally based on a workspace snapshot diff, which is a Write operation (reversible file modification). It does not execute code or irreversibly delete data, though overwriting context files could have moderate impact if done incorrectly.

From the tool's definition Refresh docs/mcp context files incrementally using workspace snapshot diff with deterministic output

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

refresh_project_context_docs Rate-limited

refresh_project_context_docs stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_project_context_docs": {
      "limits": [
        {
          "counter": "refresh_project_context_docs_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP SAPUI5 Server, so you can run agents against it safely.

FAQ

Questions about refresh_project_context_docs

What does the refresh_project_context_docs tool do? +

Refresh docs/mcp context files incrementally using workspace snapshot diff with deterministic output. It is categorised as a Write tool in the MCP SAPUI5 Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on refresh_project_context_docs? +

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

What risk level is refresh_project_context_docs? +

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

Can I rate-limit refresh_project_context_docs? +

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

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

refresh_project_context_docs is provided by the MCP SAPUI5 Server MCP server (santiagosanmartinn/mcpui5server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.