tengu_v3_intel_voter_attribution

SERVERTengu SOURCEHlobo-dev/tengu-mcp

Low RISK CLASS

Category Read

Parameters 31 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/tengu-mcp/tengu-v3-intel-voter-attribution.md

WHAT IT DOES

What tengu_v3_intel_voter_attribution does on Tengu

AI agents call tengu_v3_intel_voter_attribution to retrieve information from Tengu without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`voter`	string	—
`ticker`	string	Yes	Path parameter 'ticker' (required).
`days_back`	string	—

Parameters from the server's own tool schema.

RISK

Why tengu_v3_intel_voter_attribution is rated Low

Even though tengu_v3_intel_voter_attribution only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tengu_v3_intel_voter_attribution safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tengu, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For tengu_v3_intel_voter_attribution, this is the rule to start with:

tengu_v3_intel_voter_attribution Allowed

tengu_v3_intel_voter_attribution is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tengu_v3_intel_voter_attribution": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tengu, apply this rule, and every tengu_v3_intel_voter_attribution call is checked against it from then on.

FAQ

Questions about tengu_v3_intel_voter_attribution

What does the tengu_v3_intel_voter_attribution tool do? +

Causal attribution for a voter's score on a ticker. Instrumented voters: insider_flow (EDGAR Form-4 + insider feed, deduped by name/date/value; CEO/CFO 2x, officer 1.5x, director 1.2x weighting; contribution amounts + reconstructed score); options_flow (options-flow alerts with direction inferred from option_type+side: CALL@ASK=+1, PUT@ASK=-1, CALL@BID=-1, PUT@BID=+1; weighted by premium/median); fundamental (metadata mode — surfaces which 4 ratios the voter consumes + how to interpret). Transforms scores into EVIDENCE rather than a number. Remaining voters (sentiment, analyst_revisions, regime_hmm, technical, ml_ensemble) pending instrumentation. Optional ?voter=insider_flow|options_flow|fundamental, ?days_back=30. 15min cache. It is categorised as a Read tool in the Tengu MCP Server, which means it retrieves data without modifying state.

What parameters does tengu_v3_intel_voter_attribution accept? +

tengu_v3_intel_voter_attribution accepts 3 parameters: voter, ticker, days_back. Required: ticker. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on tengu_v3_intel_voter_attribution? +

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

What risk level is tengu_v3_intel_voter_attribution? +

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

Can I rate-limit tengu_v3_intel_voter_attribution? +

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

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

tengu_v3_intel_voter_attribution is provided by the Tengu MCP server (Hlobo-dev/tengu-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tengu, and thousands of servers like it.

This server

All 337 Tengu tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →