---
title: "Comment by X1Y1 on \"Give Your Agent Dapr's Building Blocks Through the Dapr MCP Server\" | Hashnode"
description: "Good call using allowed_tools in the Python example. The Claude Code setup gets every tool the sidecar registers, so if a secret store component is loaded, the"
url: "https://hashnode.com/posts/give-your-agent-dapr-s-building-blocks-through-the-dapr-mcp-server/6af6d7d4bc9ff87336daa693/comment/6af74209d2f6262783da4cc2"
---

[Discussion](https://hashnode.com/posts/give-your-agent-dapr-s-building-blocks-through-the-dapr-mcp-server/6af6d7d4bc9ff87336daa693)

Comment [Give Your Agent Dapr's Building Blocks Through the Dapr MCP Server](https://hashnode.com/posts/give-your-agent-dapr-s-building-blocks-through-the-dapr-mcp-server/6af6d7d4bc9ff87336daa693)

[X1Y1](https://hashnode.com/@x1y1)

[Nov 13](https://hashnode.com/posts/give-your-agent-dapr-s-building-blocks-through-the-dapr-mcp-server/6af6d7d4bc9ff87336daa693/comment/6af74209d2f6262783da4cc2)

Good call using allowed\_tools in the Python example. The Claude Code setup gets every tool the sidecar registers, so if a secret store component is loaded, the secret-reading tool comes along with invoke\_service. A deny rule for that tool in the Claude Code permissions settings closes that gap. Since it's alpha and tool names can still change, I'd also pin the go install to a release tag instead of @latest. In 10,659 public MCP configs we checked this month, two thirds of package-launched servers had no version pinned, so they ran whatever was newest at each start.
