tengu_v3_intel_news_press_releases
newswire 'Press Releases' channel — corporate press releases on the newswire (PR Newswire, Business Wire, GlobeNewswire). Use when the user asks for the company's own announcements rather than analyst/journalist coverage. 60s cache.
This record as markdown: /tools/tengu-mcp/tengu-v3-intel-news-press-releases.md
What tengu_v3_intel_news_press_releases does on Tengu
AI agents use tengu_v3_intel_news_press_releases to create or update resources in Tengu, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tengu environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | boolean | — | |
limit | integer | — | |
tickers | string | — |
Parameters from the server's own tool schema.
Why tengu_v3_intel_news_press_releases is rated Medium
An AI agent can call tengu_v3_intel_news_press_releases faster than any human can review: one bad instruction and it creates or modifies resources in Tengu by the hundred, each call as confident as the last.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs tengu_v3_intel_news_press_releases 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_news_press_releases, this is the rule to start with:
tengu_v3_intel_news_press_releases stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tengu, apply this rule, and every tengu_v3_intel_news_press_releases call is checked against it from then on.
Questions about tengu_v3_intel_news_press_releases
newswire 'Press Releases' channel — corporate press releases on the newswire (PR Newswire, Business Wire, GlobeNewswire). Use when the user asks for the company's own announcements rather than analyst/journalist coverage. 60s cache. It is categorised as a Write tool in the Tengu MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
tengu_v3_intel_news_press_releases accepts 3 parameters: body, limit, tickers. The full parameter table on this page comes from the server's own tool schema.
Register the Tengu MCP server in PolicyLayer and add a rule for tengu_v3_intel_news_press_releases: 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.
tengu_v3_intel_news_press_releases 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 tengu_v3_intel_news_press_releases 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 tengu_v3_intel_news_press_releases. 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.
tengu_v3_intel_news_press_releases 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.
More on Tengu, and thousands of servers like it.
This server
Across the catalogue