set_current_project

// WHEN AI AGENTS USE THIS TOOL

AI agents use set_current_project to create or modify resources in Zion. 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.

// WHY ENFORCE A POLICY ON SET_CURRENT_PROJECT

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

// RECOMMENDED POLICY

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

zion.yaml

tools:
  set_current_project:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Zion policy for all 7 tools.

// DETAILS

Tool Name set_current_project

Category Write

MCP Server Zion MCP Server

Risk Level Medium

// MORE ZION TOOLS

Execute reauth Write create_and_save_mock_data_recursively Write set_current_working_directory Read get_current_project Read get_project_schema Read get_projects

// WHAT CAN GO WRONG

Agents calling write-class tools like set_current_project have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Firecrawl Web Scraping Server firecrawl_generate_llmstxt AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update

// RELATED READING

// FAQ

What does the set_current_project tool do? +

Set the current project context by exId. It is categorised as a Write tool in the Zion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_current_project? +

Add a rule in your Intercept YAML policy under the tools section for set_current_project. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Zion MCP server.

What risk level is set_current_project? +

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

Can I rate-limit set_current_project? +

Yes. Add a rate_limit block to the set_current_project rule in your Intercept 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 set_current_project completely? +

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

set_current_project is provided by the Zion MCP server (zion-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.