Submit a wantlist entry telling TensorFeed what data you wish was served. Aggregated patterns inform TF's pipeline priorities. Anonymous by default, no PII collected, items expire after 30 days. Per-IP rate limit 5 submissions per 24h. Signal collector, not a contract.
AI agents use submit_wantlist_item to create or update resources in TensorFeed — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TensorFeed environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
topic | string | Yes | Short label for the data category, e.g. "real estate records" or "crypto on-chain treasury" |
description | string | Yes | 1 to 2 sentences explaining the use case. Max 500 chars. |
request_type | string | — | What kind of thing you want. Defaults to "other" if omitted. |
contact_optional | string | — | Optional contact for follow-up. Leave blank to stay anonymous. |
Parameters from the server's own tool schema.
This tool creates new wantlist entries as a form of feedback/signal collection. The data is temporary (expires in 30 days), anonymous, and designed to be aggregated for analytics rather than to perform external operations or modify critical systems. No permanent effects, no execution of code, no financial obligation, no destructive capability.
From the tool's definition Tool description explicitly states 'Submit a wantlist entry' and 'items expire after 30 days,' indicating reversible creation of data records. Rate limiting (5 submissions per 24h) and anonymous default handling confirm non-destructive nature.
Attacks that exploit this kind of access
Submit a wantlist entry telling TensorFeed what data you wish was served. Aggregated patterns inform TF's pipeline priorities. Anonymous by default, no PII collected, items expire after 30 days. Per-IP rate limit 5 submissions per 24h. Signal collector, not a contract. It is categorised as a Write tool in the TensorFeed MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
submit_wantlist_item accepts 4 parameters: topic, description, request_type, contact_optional. Required: topic, description. The full parameter table on this page comes from the server's own tool schema.
Register the TensorFeed MCP server in PolicyLayer and add a rule for submit_wantlist_item: 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 TensorFeed. Nothing to install.
submit_wantlist_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit_wantlist_item 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 submit_wantlist_item. 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.
submit_wantlist_item is provided by the TensorFeed MCP server (https://mcp.tensorfeed.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →