directory_services_cache_refresh
Refresh the directory services cache. Forces re-read of users and groups from the directory server.
This record as markdown: /tools/nasbridge/directory-services-cache-refresh.md
What directory_services_cache_refresh does on Nasbridge
AI agents invoke directory_services_cache_refresh to trigger actions in Nasbridge. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why directory_services_cache_refresh is rated High
This tool triggers an external operation (forced re-read from a directory server) rather than simply reading cached data or writing new data. It actively initiates a synchronization process with an external system. Misuse could cause temporary service disruption or load on the directory server, but effects are not permanent/destructive, making it Execute at medium severity.
From the tool's definition Refresh the directory services cache. Forces re-read of users and groups from the directory server.
Attacks that exploit this kind of access
The rule that runs directory_services_cache_refresh safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nasbridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For directory_services_cache_refresh, this is the rule to start with:
directory_services_cache_refresh stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Nasbridge, apply this rule, and every directory_services_cache_refresh call is checked against it from then on.
Questions about directory_services_cache_refresh
Refresh the directory services cache. Forces re-read of users and groups from the directory server. It is categorised as a Execute tool in the Nasbridge MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nasbridge MCP server in PolicyLayer and add a rule for directory_services_cache_refresh: 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 Nasbridge. Nothing to install.
directory_services_cache_refresh is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the directory_services_cache_refresh 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 directory_services_cache_refresh. 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.
directory_services_cache_refresh is provided by the Nasbridge MCP server (maverick0628/nasbridge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nasbridge, and thousands of servers like it.
Across the catalogue