Low Risk

get_current_project

Get information about the current project context

How to control get_current_project ↓

What get_current_project does on Claude Slack

AI agents call get_current_project to retrieve information from Claude Slack without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_current_project needs a policy

This tool retrieves project context information without modifying, executing, or deleting any data. It is a read-only query operation with minimal blast radius if misused—an agent could only learn about existing project information. No financial, destructive, or execution-based actions are possible.

From the tool's definition Tool name 'get_current_project' and description 'Get information about the current project context' indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_current_project gives an agent:

How to control get_current_project

PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Slack, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_project:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_current_project": {}
  }
}

get_current_project is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Claude Slack — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_current_project

What does the get_current_project tool do? +

Get information about the current project context. It is categorised as a Read tool in the Claude Slack MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_current_project? +

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

What risk level is get_current_project? +

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

Can I rate-limit get_current_project? +

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

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

get_current_project is provided by the Claude Slack MCP server (theo-nash/claude-slack). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claude Slack tool call.

Start from Claude Slack, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

19 Claude Slack tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.