[EXPERIMENTAL] List all parent segments (audiences) in Customer Data Platform. No parameters required.
AI agents call list_parent_segments to retrieve information from Treasure Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of parent segments/audiences from the CDP without modifying, deleting, or executing any operations. It is a pure data retrieval function with minimal blast radius if misused—worst case being information disclosure of audience names.
From the tool's definition Tool name 'list_parent_segments' with description 'List all parent segments' indicates a retrieval operation. The phrase 'No parameters required' and the context of listing existing data confirm read-only behavior with no side effects.
Documented attack patterns abuse exactly the kind of access list_parent_segments gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Treasure Data MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_parent_segments:
{
"version": "1",
"default": "deny",
"tools": {
"list_parent_segments": {}
}
} list_parent_segments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
[EXPERIMENTAL] List all parent segments (audiences) in Customer Data Platform. No parameters required. It is categorised as a Read tool in the Treasure Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Treasure Data MCP Server MCP server in PolicyLayer and add a rule for list_parent_segments: 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 Treasure Data MCP Server. Nothing to install.
list_parent_segments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_parent_segments 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 list_parent_segments. 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.
list_parent_segments is provided by the Treasure Data MCP Server MCP server (treasure-data/td-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Treasure Data MCP Server, 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.
23 Treasure Data MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.